Linaro-mm-sig May 2026

linaro-mm-sig@lists.linaro.org

97 participants
341 discussions

by divedtomson＠gmail.com

1 hour, 49 minutes

Re: [PATCH] drm/prime: Fix unsupervised rb_tree corruption in drm_prime_remove_buf_handle

by kernel test robot

Hello, kernel test robot noticed "WARNING:possible_recursive_locking_detected" on: commit: 60a023d26c97753be2beee6062d71ce9416725b1 ("[PATCH] drm/prime: Fix unsupervised rb_tree corruption in drm_prime_remove_buf_handle") url: https://github.com/intel-lab-lkp/linux/commits/w15303746062-163-com/drm-pri… base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next patch link: https://lore.kernel.org/all/20260528082912.1051262-1-w15303746062@163.com/ patch subject: [PATCH] drm/prime: Fix unsupervised rb_tree corruption in drm_prime_remove_buf_handle in testcase: boot config: x86_64-rhel-9.4-bpf compiler: gcc-14 test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G (please refer to attached dmesg/kmsg for entire log/backtrace) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot <oliver.sang(a)intel.com> | Closes: https://lore.kernel.org/oe-lkp/202605310941.ddd52610-lkp@intel.com [ 86.630882][ T218] WARNING: possible recursive locking detected [ 86.631312][ T218] 7.1.0-rc2+ #1 Not tainted [ 86.631634][ T218] -------------------------------------------- [ 86.632065][ T218] (udev-worker)/218 is trying to acquire lock: [ 86.632529][ T218] ffff8881ab017388 (&prime_fpriv->lock){+.+.}-{4:4}, at: drm_prime_remove_buf_handle (gpu/drm/drm_prime.c:195) drm [ 86.633434][ T218] [ 86.633434][ T218] but task is already holding lock: [ 86.633951][ T218] ffff8881ab017388 (&prime_fpriv->lock){+.+.}-{4:4}, at: drm_gem_object_release_handle (gpu/drm/drm_gem.c:377) drm [ 86.638664][ T218] [ 86.638664][ T218] other info that might help us debug this: [ 86.639229][ T218] Possible unsafe locking scenario: [ 86.639229][ T218] [ 86.639769][ T218] CPU0 [ 86.640006][ T218] ---- [ 86.640243][ T218] lock(&prime_fpriv->lock); [ 86.640581][ T218] lock(&prime_fpriv->lock); [ 86.640916][ T218] [ 86.640916][ T218] *** DEADLOCK *** [ 86.640916][ T218] [ 86.641480][ T218] May be due to missing lock nesting notation [ 86.641480][ T218] [ 86.642060][ T218] 4 locks held by (udev-worker)/218: [ 86.642446][ T218] #0: ffff8881022921f8 (&dev->mutex){....}-{4:4}, at: __driver_attach (linux/device.h:1040 base/dd.c:1174 base/dd.c:1294) [ 86.643133][ T218] #1: ffff8881ab020260 (&dev->clientlist_mutex){+.+.}-{4:4}, at: drm_client_register (gpu/drm/drm_client.c:129) drm [ 86.644051][ T218] #2: ffff8882a2b58a70 (&helper->lock){+.+.}-{4:4}, at: drm_fb_helper_initial_config (gpu/drm/drm_fb_helper.c:1717 gpu/drm/drm_fb_helper.c:1710) drm_kms_helper [ 86.644930][ T218] #3: ffff8881ab017388 (&prime_fpriv->lock){+.+.}-{4:4}, at: drm_gem_object_release_handle (gpu/drm/drm_gem.c:377) drm [ 86.645880][ T218] [ 86.645880][ T218] stack backtrace: [ 86.646300][ T218] CPU: 1 UID: 0 PID: 218 Comm: (udev-worker) Not tainted 7.1.0-rc2+ #1 PREEMPT(full) [ 86.646307][ T218] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 86.646311][ T218] Call Trace: [ 86.646316][ T218] <TASK> [ 86.646321][ T218] dump_stack_lvl (dump_stack.c:94 dump_stack.c:120) [ 86.646333][ T218] print_deadlock_bug.cold (locking/lockdep.c:3041) [ 86.646341][ T218] validate_chain (locking/lockdep.c:3093 locking/lockdep.c:3895) [ 86.646350][ T218] __lock_acquire (locking/lockdep.c:5237) [ 86.646366][ T218] lock_acquire (trace/events/lock.h:24 (discriminator 15) trace/events/lock.h:24 (discriminator 15) locking/lockdep.c:5831 (discriminator 15)) [ 86.646372][ T218] ? drm_prime_remove_buf_handle (gpu/drm/drm_prime.c:195) drm [ 86.646516][ T218] ? rcu_is_watching (x86/include/asm/atomic.h:23 linux/atomic/atomic-arch-fallback.h:457 linux/context_tracking.h:128 rcu/tree.c:752) [ 86.646521][ T218] ? drm_prime_remove_buf_handle (gpu/drm/drm_prime.c:195) drm [ 86.646659][ T218] ? lock_acquire (trace/events/lock.h:24 (discriminator 21) locking/lockdep.c:5831 (discriminator 21)) [ 86.646665][ T218] __mutex_lock (locking/mutex.c:646 locking/mutex.c:820) [ 86.646675][ T218] ? drm_prime_remove_buf_handle (gpu/drm/drm_prime.c:195) drm [ 86.646814][ T218] ? drm_prime_remove_buf_handle (gpu/drm/drm_prime.c:195) drm [ 86.646952][ T218] ? __mutex_lock (locking/mutex.c:656 locking/mutex.c:820) [ 86.646958][ T218] ? drm_gem_object_release_handle (gpu/drm/drm_gem.c:377) drm [ 86.647103][ T218] ? __pfx___mutex_lock (locking/mutex.c:914) [ 86.647109][ T218] ? __pfx___mutex_lock (locking/mutex.c:914) [ 86.647116][ T218] ? idr_replace (idr.c:304) [ 86.647124][ T218] ? drm_prime_remove_buf_handle (gpu/drm/drm_prime.c:195) drm [ 86.647264][ T218] drm_prime_remove_buf_handle (gpu/drm/drm_prime.c:195) drm [ 86.647408][ T218] drm_gem_object_release_handle (gpu/drm/drm_gem.c:379) drm [ 86.647555][ T218] drm_gem_handle_delete (gpu/drm/drm_gem.c:413) drm [ 86.647700][ T218] drm_client_buffer_create_dumb (gpu/drm/drm_client.c:424) drm [ 86.647840][ T218] ? __pfx_drm_client_buffer_create_dumb (gpu/drm/drm_client.c:267) drm [ 86.647977][ T218] ? drm_fb_helper_single_fb_probe (gpu/drm/drm_fb_helper.c:1414 gpu/drm/drm_fb_helper.c:1445) drm_kms_helper [ 86.648030][ T218] drm_fbdev_shmem_driver_fbdev_probe (gpu/drm/drm_fbdev_shmem.c:151) drm_shmem_helper [ 86.648045][ T218] ? __pfx_drm_fbdev_shmem_driver_fbdev_probe (gpu/drm/drm_fbdev_shmem.c:119) drm_shmem_helper [ 86.648055][ T218] ? __kmalloc_noprof (linux/local_lock_internal.h:62 slub.c:4771 slub.c:4883 slub.c:5294 slub.c:5307) [ 86.648064][ T218] ? rcu_is_watching (x86/include/asm/atomic.h:23 linux/atomic/atomic-arch-fallback.h:457 linux/context_tracking.h:128 rcu/tree.c:752) [ 86.648073][ T218] drm_fb_helper_single_fb_probe (gpu/drm/drm_fb_helper.c:1454) drm_kms_helper [ 86.648121][ T218] ? __pfx_drm_fb_helper_single_fb_probe (gpu/drm/drm_fb_helper.c:1391) drm_kms_helper [ 86.648167][ T218] ? fb_copy_cmap (video/fbdev/core/fbcmap.c:187) [ 86.648174][ T218] ? fb_alloc_cmap_gfp (video/fbdev/core/fbcmap.c:124 (discriminator 1)) [ 86.648180][ T218] __drm_fb_helper_initial_config_and_unlock (gpu/drm/drm_fb_helper.c:1635) drm_kms_helper [ 86.648230][ T218] drm_fbdev_client_hotplug (gpu/drm/clients/drm_fbdev_client.c:66) drm_client_lib [ 86.648239][ T218] drm_client_register (gpu/drm/drm_client.c:143) drm [ 86.648376][ T218] drm_fbdev_client_setup (gpu/drm/clients/drm_fbdev_client.c:168) drm_client_lib [ 86.648383][ T218] drm_client_setup (gpu/drm/clients/drm_client_setup.c:46 gpu/drm/clients/drm_client_setup.c:35) drm_client_lib [ 86.648390][ T218] bochs_pci_probe (gpu/drm/tiny/bochs.c:776 gpu/drm/tiny/bochs.c:747) bochs [ 86.648405][ T218] ? __pfx_bochs_pci_probe (gpu/drm/tiny/bochs.c:254) bochs [ 86.648413][ T218] local_pci_probe (pci/pci-driver.c:325) [ 86.648422][ T218] pci_call_probe (pci/pci-driver.c:387) [ 86.648427][ T218] ? __pfx_pci_call_probe (pci/pci-driver.c:653) [ 86.648432][ T218] ? find_held_lock (locking/lockdep.c:5350) [ 86.648439][ T218] ? pci_match_device (linux/spinlock.h:390 pci/pci-driver.c:156) [ 86.648444][ T218] ? rcu_is_watching (x86/include/asm/atomic.h:23 linux/atomic/atomic-arch-fallback.h:457 linux/context_tracking.h:128 rcu/tree.c:752) [ 86.648448][ T218] ? trace_preempt_on (trace/events/preemptirq.h:53 (discriminator 21) trace/trace_preemptirq.c:120 (discriminator 21)) [ 86.648452][ T218] ? pci_match_id (pci/pci.h:466 pci/pci.h:460 pci/pci-driver.c:110) [ 86.648459][ T218] ? pci_match_device (pci/pci-driver.c:168) [ 86.648465][ T218] pci_device_probe (pci/pci-driver.c:448 pci/pci-driver.c:482) [ 86.648471][ T218] call_driver_probe (base/dd.c:631) [ 86.648477][ T218] really_probe (base/dd.c:709) [ 86.648484][ T218] __driver_probe_device (base/dd.c:871) [ 86.648489][ T218] driver_probe_device (base/dd.c:901) [ 86.648495][ T218] __driver_attach (base/dd.c:1295) [ 86.648500][ T218] ? __pfx___driver_attach (base/dd.c:1004 (discriminator 1)) [ 86.648504][ T218] bus_for_each_dev (base/bus.c:383) [ 86.648511][ T218] ? __pfx_bus_for_each_dev (base/bus.c:205) [ 86.648516][ T218] ? bus_add_driver (base/bus.c:754) [ 86.648520][ T218] ? trace_preempt_on (trace/events/preemptirq.h:53 (discriminator 21) trace/trace_preemptirq.c:120 (discriminator 21)) [ 86.648526][ T218] bus_add_driver (base/bus.c:756) [ 86.648532][ T218] driver_register (base/driver.c:249) [ 86.648538][ T218] ? __pfx_bochs_pci_driver_init (bochs.c:?) bochs [ 86.648548][ T218] do_one_initcall (main.c:1392) [ 86.648555][ T218] ? __pfx_do_one_initcall (trace/events/initcall.h:10) [ 86.648561][ T218] ? kasan_unpoison (kasan/shadow.c:146 kasan/shadow.c:178) [ 86.648568][ T218] ? __kasan_slab_alloc (kasan/common.c:336 kasan/common.c:366) [ 86.648575][ T218] ? rcu_is_watching (x86/include/asm/atomic.h:23 linux/atomic/atomic-arch-fallback.h:457 linux/context_tracking.h:128 rcu/tree.c:752) [ 86.648579][ T218] ? kasan_unpoison (kasan/shadow.c:146 kasan/shadow.c:178) [ 86.648586][ T218] do_init_module (module/main.c:3106) [ 86.648594][ T218] ? __pfx_do_init_module (trace/events/module.h:50 (discriminator 1)) [ 86.648599][ T218] ? load_module (module/main.c:2528 module/main.c:2523 module/main.c:3575) [ 86.648603][ T218] ? kfree (linux/kasan.h:235 slub.c:2689 slub.c:6250 slub.c:6565) [ 86.648611][ T218] load_module (module/main.c:3580) [ 86.648620][ T218] ? __pfx_load_module (module/main.c:3020) [ 86.648626][ T218] ? __pfx_kernel_read_file (??:?) [ 86.648632][ T218] ? do_syscall_64 (linux/irq-entry-common.h:279 linux/entry-common.h:320 x86/entry/syscall_64.c:100) [ 86.648640][ T218] init_module_from_file (module/main.c:3777) [ 86.648646][ T218] ? __pfx_init_module_from_file (module/main.c:3634) [ 86.648656][ T218] ? idempotent_init_module (linux/spinlock.h:390 module/main.c:3688 module/main.c:3788) [ 86.648661][ T218] ? rcu_is_watching (x86/include/asm/atomic.h:23 linux/atomic/atomic-arch-fallback.h:457 linux/context_tracking.h:128 rcu/tree.c:752) [ 86.648664][ T218] ? trace_preempt_on (trace/events/preemptirq.h:53 (discriminator 21) trace/trace_preemptirq.c:120 (discriminator 21)) [ 86.648669][ T218] ? preempt_count_sub (sched/core.c:5874 (discriminator 2) sched/core.c:5871 (discriminator 2) sched/core.c:5893 (discriminator 2)) [ 86.648676][ T218] idempotent_init_module (module/main.c:3789) [ 86.648682][ T218] ? __pfx_idempotent_init_module (module/main.c:3778) [ 86.648687][ T218] ? preempt_count_sub (sched/core.c:5874 (discriminator 2) sched/core.c:5871 (discriminator 2) sched/core.c:5893 (discriminator 2)) [ 86.648696][ T218] ? security_capable (security.c:660 (discriminator 20)) [ 86.648702][ T218] __x64_sys_finit_module (module/main.c:3815 module/main.c:3799 module/main.c:3799) [ 86.648708][ T218] do_syscall_64 (x86/entry/syscall_64.c:63 x86/entry/syscall_64.c:94) [ 86.648713][ T218] ? rcu_is_watching (x86/include/asm/atomic.h:23 linux/atomic/atomic-arch-fallback.h:457 linux/context_tracking.h:128 rcu/tree.c:752) [ 86.648717][ T218] ? trace_preempt_on (trace/events/preemptirq.h:53 (discriminator 21) trace/trace_preemptirq.c:120 (discriminator 21)) [ 86.648720][ T218] ? do_syscall_64 (linux/randomize_kstack.h:58 x86/entry/syscall_64.c:92) [ 86.648725][ T218] ? preempt_count_sub (sched/core.c:5874 (discriminator 2) sched/core.c:5871 (discriminator 2) sched/core.c:5893 (discriminator 2)) [ 86.648730][ T218] ? do_syscall_64 (linux/randomize_kstack.h:58 x86/entry/syscall_64.c:92) [ 86.648734][ T218] ? irqentry_exit (linux/irq-entry-common.h:280 linux/irq-entry-common.h:325 entry/common.c:162) [ 86.648740][ T218] entry_SYSCALL_64_after_hwframe (x86/entry/entry_64.S:121) [ 86.648747][ T218] RIP: 0033:0x7f3757f90779 [ 86.648768][ T218] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 4f 86 0d 00 f7 d8 64 89 01 48 All code ======== 0: ff c3 inc %ebx 2: 66 2e 0f 1f 84 00 00 cs nopw 0x0(%rax,%rax,1) 9: 00 00 00 c: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1) 11: 48 89 f8 mov %rdi,%rax 14: 48 89 f7 mov %rsi,%rdi 17: 48 89 d6 mov %rdx,%rsi 1a: 48 89 ca mov %rcx,%rdx 1d: 4d 89 c2 mov %r8,%r10 20: 4d 89 c8 mov %r9,%r8 23: 4c 8b 4c 24 08 mov 0x8(%rsp),%r9 28: 0f 05 syscall 2a:* 48 3d 01 f0 ff ff cmp $0xfffffffffffff001,%rax <-- trapping instruction 30: 73 01 jae 0x33 32: c3 ret 33: 48 8b 0d 4f 86 0d 00 mov 0xd864f(%rip),%rcx # 0xd8689 3a: f7 d8 neg %eax 3c: 64 89 01 mov %eax,%fs:(%rcx) 3f: 48 rex.W The kernel config and materials to reproduce are available at: https://download.01.org/0day-ci/archive/20260531/202605310941.ddd52610-lkp@… -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

2 hours, 1 minute

A Beginner's Guide to Geometry Dash

by marleneostetler＠wshu.net

Ever found yourself captivated by the rhythmic thumping and vibrant visuals of a game where a block navigates a perilous obstacle course? That's the essence of Geometry Dash, a deceptively simple yet endlessly engaging rhythm-based platformer that has garnered a massive following. If you're looking to dive into a game that tests your reflexes, spatial awareness, and musicality, you've come to the right place. This guide will walk you through the basics of experiencing this unique title, offering tips and insights for both newcomers and those looking to improve. What is Geometry Dash? A Symphony of Squares and Spikes At its core, geometry dash is about guiding a square-shaped icon through a series of levels, each meticulously synchronized to an energetic electronic soundtrack. The objective is straightforward: reach the end of the level without crashing into any obstacles. These obstacles range from stationary spikes and moving saws to gravity-altering portals and speed-changing gates. The beauty of Geometry Dash lies in its elegant simplicity – a single tap or click makes your icon jump. Hold down, and it will continuously jump (or fly, depending on the current game mode). https://geometrydashlitefree.com The game isn't just about pixel-perfect timing; it's also about memorization and pattern recognition. Each level is a carefully choreographed dance between your icon and the environment. While the initial levels serve as a tutorial of sorts, introducing new mechanics and obstacles gradually, the difficulty quickly ramps up, demanding precise execution and a keen ear for the music's rhythm. The satisfaction of finally conquering a particularly challenging section, after countless attempts, is a feeling few other games can replicate. Getting Started: Your First Jumps and Flips Jumping into geometry dash is surprisingly easy. Most versions of the game offer a "Lite" or free demo, allowing you to experience a taste of the action without commitment. Once you've launched the game, you'll likely be presented with a selection of official levels, each with its own unique theme, music, and difficulty rating. Start with the earliest levels, such as "Stereo Madness" or "Back on Track." These are designed to introduce you to the fundamental mechanics: the basic jump, the continuous jump, and how the music dictates the flow of the level. Don't be discouraged by early failures; dying is an integral part of the learning process in Geometry Dash. Each failed attempt offers a valuable lesson, revealing the timing of a jump or the placement of an obstacle you hadn't noticed before. As you progress, you'll encounter various game modes, each changing how your icon behaves: Cube: The standard jumping icon. Ship: Your icon transforms into a spaceship, allowing you to fly by holding down. Releasing the button causes you to descend. Ball: Gravity flips with each tap, making your icon roll along the ceiling or floor. UFO: Similar to the ship, but each tap causes a short burst of upward flight. Wave: Your icon moves in a diagonal wave pattern, controlled by holding down to go up and releasing to go down. Robot: A bouncier version of the cube, with adjustable jump height based on how long you hold down. Spider: Instantly teleports your icon between the floor and ceiling with each tap. Mastering these modes, and understanding how they interact with different portals and environmental elements, is key to success. Tips for Taming the Dash Geometry Dash can be frustrating, but with the right approach, it becomes incredibly rewarding. Here are some tips to help you on your journey: Start Slow and Steady: Don't immediately jump into demon levels. Work your way through the official levels in order, gradually building your skills and understanding of the game's mechanics. Practice Mode is Your Best Friend: Every level features a "Practice Mode" where you can place checkpoints. This allows you to tackle difficult sections repeatedly without having to restart the entire level. Utilize it extensively to learn tricky timings and obstacle patterns. Listen to the Music: The music isn't just background noise; it's a vital part of the gameplay. Many jumps and actions are synchronized with the beat, so paying attention to the rhythm can significantly improve your timing. Focus on One Section at a Time: If you're struggling with a particular part of a level, break it down. Practice that specific sequence in practice mode until you can consistently clear it. Don't Be Afraid to Take Breaks: Frustration can quickly set in. If you find yourself getting angry or making more mistakes, step away from the game for a bit. A fresh perspective can often work wonders. Experiment with Custom Levels: Once you've tackled the official levels, the community-created levels offer an endless supply of challenges and creativity. From auto levels to extreme demons, there's something for everyone. The Endless Dash Geometry Dash is more than just a game; it's a testament to dedication and perseverance. Its simple controls belie a deep and challenging experience that rewards patience and practice. Whether you're aiming to conquer every official level, create your own elaborate courses, or simply enjoy the captivating music and visuals, the world of Geometry Dash offers endless possibilities. So, grab your virtual square, crank up the volume, and prepare for an exhilarating ride through a vibrant, spike-filled world.

1 day, 3 hours

Re: [PATCH v2 1/9] PCI/P2PDMA: Add CONFIG_PCI_P2PDMA_CORE

by Jason Gunthorpe

On Wed, May 27, 2026 at 03:09:46PM -0600, Alex Williamson wrote: > This deserves a /* CONFIG_PCI_P2PDMA */ reference like the previous > long span, though potentially a better solution would be to split the > core code out to a separate file with shared header. I asked opus to > see what this would look like and it generated the patch below > (unverified, compile tested only). Bigger diff, harder to follow > blame, but the shape of the core is much more apparent. You're welcome > to take or leave it. I think it is a good idea, it will make it easier to add more stuff to these different aspects. Really they are now two different things with one layered on top of the other. Jason

1 day, 10 hours

TELEGRAM: DRMIKE100 TO BUY ADDERALL ONLINE WITHOUT SCRIPT

by humanhealthchems＠gmail.com

TELEGRAM: DRMIKE100 TO BUY ADDERALL IN JAPAN WITHOUT SCRIPT Looking to enhance focus, improve cognitive performance, and manage attention deficit hyperactivity disorder (ADHD) symptoms? Look no further than the latest stock of Adderall available online! With just a few clicks, you can conveniently buy Adderall online and experience the unparalleled benefits it offers. Harnessing the power of its active ingredients - amphetamine and dextroamphetamine - this medication stimulates the central nervous system, helping individuals maintain better concentration levels while curbing impulsivity. Whether you're a student preparing for exams or an adult seeking enhanced productivity at work, buying Adderall online opens up a world of possibilities for achieving your goals efficiently. Rest assured that our quality-controlled inventory guarantees authentic products that are safe and effective. Say goodbye to distractions and hello to laser-like focus with Buy Adderall Online! Unlock a world of convenience with our hassle-free solution – buy Adderall online, without the need for a visit to the doctor's office. Embrace efficiency and reclaim your time with a seamless online experience. Experience the freedom to manage your well-being on your terms. Say goodbye to lengthy appointments and embrace the simplicity of obtaining Buy Adderall from the comfort of your own space. No more waiting rooms, no more delays – just a straightforward process tailored to your needs. Buy Adderal Buy Adderall Online 30 mg Buy Adderall XR Online 30 mg

1 day, 14 hours

TELEGRAM: DRMIKE100 TO BUY ADDERALL 30MG ONLINE WITHOUT PRESCRIPTION

by humanhealthchems＠gmail.com

Looking to enhance focus, improve cognitive performance, and manage attention deficit hyperactivity disorder (ADHD) symptoms? Look no further than the latest stock of Adderall available online! With just a few clicks, you can conveniently buy Adderall online and experience the unparalleled benefits it offers. Harnessing the power of its active ingredients - amphetamine and dextroamphetamine - this medication stimulates the central nervous system, helping individuals maintain better concentration levels while curbing impulsivity. Whether you're a student preparing for exams or an adult seeking enhanced productivity at work, buying Adderall online opens up a world of possibilities for achieving your goals efficiently. Rest assured that our quality-controlled inventory guarantees authentic products that are safe and effective. Say goodbye to distractions and hello to laser-like focus with Buy Adderall Online! Unlock a world of convenience with our hassle-free solution – buy Adderall online, without the need for a visit to the doctor's office. Embrace efficiency and reclaim your time with a seamless online experience. Experience the freedom to manage your well-being on your terms. Say goodbye to lengthy appointments and embrace the simplicity of obtaining Buy Adderall from the comfort of your own space. No more waiting rooms, no more delays – just a straightforward process tailored to your needs. Buy Adderal Buy Adderall Online 30 mg Buy Adderall XR Online 30 mg

1 day, 14 hours

[PATCH v15 0/6] Rust bindings for gem shmem

by Lyude Paul

Most of this patch series has already been pushed upstream, this is just the second half of the patch series that has not been pushed yet + some additional changes which were required to implement changes requested by the mailing list. This patch series is originally from Asahi, previously posted by Daniel Almeida. The previous version of the patch series can be found here: https://patchwork.freedesktop.org/series/164580/ Branch with patches applied available here: https://gitlab.freedesktop.org/lyudess/linux/-/commits/rust/gem-shmem This patch series applies on top of drm-rust-next with the following dependencies applied: https://lore.kernel.org/rust-for-linux/20260529173137.303717-1-lyude@redhat… Lyude Paul (6): rust: gem: shmem: Fix Default implementation for ObjectConfig rust: drm: gem/shmem: Add DmaResvGuard helper rust: drm: gem: Add vmap functions to shmem bindings rust: faux: Allow retrieving a bound Device drm/gem/shmem: Introduce __drm_gem_shmem_free_sgt_locked() rust: drm: gem: Introduce shmem::Object::sg_table() drivers/gpu/drm/drm_gem_shmem_helper.c | 32 +- include/drm/drm_gem_shmem_helper.h | 1 + rust/kernel/drm/gem/shmem.rs | 497 ++++++++++++++++++++++++- rust/kernel/faux.rs | 7 +- 4 files changed, 512 insertions(+), 25 deletions(-) base-commit: 0e42ec83d46ab8877d38d37493328ed7d1a24de8 prerequisite-patch-id: c8ade07eec6e9c9e875800b114137c459d362e4e prerequisite-patch-id: c38da06dbc4cfd2589bf2e7e9f0ebaa4da521ddf -- 2.54.0

1 day, 15 hours

[PATCH] drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_format

by Mikhail Gavrilov

When dumping IB contents from a hung job, amdgpu_devcoredump_format() acquires the VM root PD's reservation lock via amdgpu_vm_lock_by_pasid() and then, for each IB referenced by the job, calls amdgpu_bo_reserve() on the BO that backs the IB. Both reservations are taken on reservation_ww_class_mutex objects but neither uses a ww_acquire_ctx, which trips lockdep: WARNING: possible recursive locking detected -------------------------------------------- kworker/u128:0 is trying to acquire lock: ffff88838b16e1f0 (reservation_ww_class_mutex){+.+.}-{4:4}, at: amdgpu_devcoredump_format+0x1594/0x23f0 [amdgpu] but task is already holding lock: ffff8882f82681f0 (reservation_ww_class_mutex){+.+.}-{4:4}, at: amdgpu_devcoredump_format+0x1594/0x23f0 [amdgpu] Possible unsafe locking scenario: CPU0 ---- lock(reservation_ww_class_mutex); lock(reservation_ww_class_mutex); *** DEADLOCK *** May be due to missing lock nesting notation Workqueue: events_unbound amdgpu_devcoredump_deferred_work [amdgpu] Call Trace: __ww_mutex_lock.constprop.0 ww_mutex_lock amdgpu_bo_reserve amdgpu_devcoredump_format+0x1594 [amdgpu] amdgpu_devcoredump_deferred_work+0xea [amdgpu] process_one_work worker_thread kthread The two reservations are on different BOs in the captured trace, so the splat is a lockdep-correctness warning, not an observed deadlock. It becomes a real self-deadlock whenever the IB BO shares its dma_resv with the root PD (the always-valid case, see amdgpu_vm_is_bo_always_valid()): amdgpu_bo_reserve(abo) re-acquires the same ww_mutex without a ticket and blocks forever. With amdgpu.gpu_recovery=0 the timeout handler refires every ~2 s and each invocation produces this splat, drowning the kernel ring buffer. Fix it by collecting the per-IB BO references under the root PD's reservation, then releasing the root before reserving each IB BO individually. The walk over the VM mapping tree must remain under the root lock (mappings can be torn down without it), but the actual content copies do not need to nest inside it. Each per-IB reservation is now an independent top-level acquire, eliminating the nested ww_mutex. The collect/release logic is factored out into two small helpers (amdgpu_devcoredump_collect_ib_refs / amdgpu_devcoredump_release_ib_refs) to keep the main function's indentation reasonable. This also fixes a BO refcount leak in the original code: when amdgpu_bo_reserve() failed, control jumped to free_ib_content without running amdgpu_bo_unref(). In the new structure the per-IB BO refs are released unconditionally in the cleanup helper. Reproducer (~150 LoC libdrm_amdgpu): submit a single GFX IB containing PACKET3_INDIRECT_BUFFER chained at GPU VA 0 and wait for the fence. The TDR fires within ~10 s and the deferred coredump worker produces the splat above on every invocation. Fixes: 7b15fc2d1f1a ("drm/amdgpu: dump job ibs in the devcoredump") Cc: stable(a)vger.kernel.org # 7.1 Signed-off-by: Mikhail Gavrilov <mikhail.v.gavrilov(a)gmail.com> --- .../gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c | 147 +++++++++++++----- 1 file changed, 110 insertions(+), 37 deletions(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c index d386bc775d03..f6bb968de756 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c @@ -207,6 +207,72 @@ static void amdgpu_devcoredump_fw_info(struct amdgpu_device *adev, } } +struct amdgpu_devcoredump_ib_ref { + struct amdgpu_bo *bo; + u64 offset; +}; + +/* + * Walk the VM's mapping tree under the root PD's reservation to obtain the BO + * that backs each IB and pin it with a refcount. The root PD reservation is + * dropped before this function returns; the caller can then reserve each IB + * BO individually without nesting ww_mutex acquires on + * reservation_ww_class_mutex. + * + * Returns an array of num_ibs entries (each ib_refs[i].bo may be NULL if its + * mapping was not found), or NULL on allocation failure / VM lookup failure. + * The caller must release the BO refs and free the array. + */ +static struct amdgpu_devcoredump_ib_ref * +amdgpu_devcoredump_collect_ib_refs(struct amdgpu_device *adev, + struct amdgpu_coredump_info *coredump) +{ + struct amdgpu_devcoredump_ib_ref *ib_refs; + struct amdgpu_bo_va_mapping *mapping; + struct amdgpu_bo *root; + struct amdgpu_vm *vm; + u64 va_start; + + ib_refs = kcalloc(coredump->num_ibs, sizeof(*ib_refs), GFP_KERNEL); + if (!ib_refs) + return NULL; + + vm = amdgpu_vm_lock_by_pasid(adev, &root, coredump->pasid); + if (!vm) { + kfree(ib_refs); + return NULL; + } + + for (int i = 0; i < coredump->num_ibs; i++) { + va_start = coredump->ibs[i].gpu_addr & AMDGPU_GMC_HOLE_MASK; + mapping = amdgpu_vm_bo_lookup_mapping(vm, va_start / AMDGPU_GPU_PAGE_SIZE); + if (!mapping) + continue; + + ib_refs[i].bo = amdgpu_bo_ref(mapping->bo_va->base.bo); + ib_refs[i].offset = va_start - + mapping->start * AMDGPU_GPU_PAGE_SIZE; + } + + amdgpu_bo_unreserve(root); + amdgpu_bo_unref(&root); + + return ib_refs; +} + +static void +amdgpu_devcoredump_release_ib_refs(struct amdgpu_devcoredump_ib_ref *ib_refs, + int num_ibs) +{ + if (!ib_refs) + return; + + for (int i = 0; i < num_ibs; i++) + if (ib_refs[i].bo) + amdgpu_bo_unref(&ib_refs[i].bo); + kfree(ib_refs); +} + static ssize_t amdgpu_devcoredump_format(char *buffer, size_t count, struct amdgpu_coredump_info *coredump) { @@ -214,13 +280,11 @@ amdgpu_devcoredump_format(char *buffer, size_t count, struct amdgpu_coredump_inf struct drm_printer p; struct drm_print_iterator iter; struct amdgpu_vm_fault_info *fault_info; - struct amdgpu_bo_va_mapping *mapping; struct amdgpu_ip_block *ip_block; struct amdgpu_res_cursor cursor; - struct amdgpu_bo *abo, *root; - uint64_t va_start, offset; + struct amdgpu_bo *abo; + uint64_t offset; struct amdgpu_ring *ring; - struct amdgpu_vm *vm; u32 *ib_content; uint8_t *kptr; int ver, i, j, r; @@ -343,43 +407,52 @@ amdgpu_devcoredump_format(char *buffer, size_t count, struct amdgpu_coredump_inf drm_printf(&p, "VRAM is lost due to GPU reset!\n"); if (coredump->num_ibs) { - /* Don't try to lookup the VM or map the BOs when calculating the - * size required to store the devcoredump. + struct amdgpu_devcoredump_ib_ref *ib_refs = NULL; + + /* + * Snapshot per-IB BO references under the root PD's reservation, + * then release the root before reserving each IB BO individually + * to copy its contents. + * + * Reserving an IB BO while the root PD is still reserved would + * be a nested ww_mutex acquire on reservation_ww_class_mutex + * without a ww_acquire_ctx, which trips lockdep's recursive- + * locking check and self-deadlocks for IB BOs that share their + * dma_resv with the root PD (always-valid BOs). + * + * Skip lookup/reservation entirely on the sizing pass: it does + * not write IB content, and the size estimate doesn't depend on + * whether the BOs are reachable. */ - if (sizing_pass) - vm = NULL; - else - vm = amdgpu_vm_lock_by_pasid(adev, &root, coredump->pasid); + if (!sizing_pass) + ib_refs = amdgpu_devcoredump_collect_ib_refs(adev, coredump); - for (int i = 0; i < coredump->num_ibs && (sizing_pass || vm); i++) { + for (int i = 0; i < coredump->num_ibs; i++) { ib_content = kvmalloc_array(coredump->ibs[i].ib_size_dw, 4, GFP_KERNEL); if (!ib_content) continue; - /* vm=NULL can only happen when 'sizing_pass' is true. Skip to the - * drm_printf() calls (ib_content doesn't need to be initialized - * as its content won't be written anywhere). - */ - if (!vm) + if (sizing_pass) goto output_ib_content; - va_start = coredump->ibs[i].gpu_addr & AMDGPU_GMC_HOLE_MASK; - mapping = amdgpu_vm_bo_lookup_mapping(vm, va_start / AMDGPU_GPU_PAGE_SIZE); - if (!mapping) - goto free_ib_content; + if (!ib_refs || !ib_refs[i].bo) + goto output_ib_content; + + abo = ib_refs[i].bo; + offset = ib_refs[i].offset; - offset = va_start - (mapping->start * AMDGPU_GPU_PAGE_SIZE); - abo = amdgpu_bo_ref(mapping->bo_va->base.bo); r = amdgpu_bo_reserve(abo, false); if (r) - goto free_ib_content; + goto output_ib_content; if (abo->flags & AMDGPU_GEM_CREATE_NO_CPU_ACCESS) { off = 0; - if (abo->tbo.resource->mem_type != TTM_PL_VRAM) - goto unreserve_abo; + if (abo->tbo.resource->mem_type != TTM_PL_VRAM) { + amdgpu_bo_unreserve(abo); + goto output_ib_content; + } amdgpu_res_first(abo->tbo.resource, offset, coredump->ibs[i].ib_size_dw * 4, @@ -395,8 +468,10 @@ amdgpu_devcoredump_format(char *buffer, size_t count, struct amdgpu_coredump_inf r = ttm_bo_kmap(&abo->tbo, 0, PFN_UP(abo->tbo.base.size), &abo->kmap); - if (r) - goto unreserve_abo; + if (r) { + amdgpu_bo_unreserve(abo); + goto output_ib_content; + } kptr = amdgpu_bo_kptr(abo); kptr += offset; @@ -406,21 +481,19 @@ amdgpu_devcoredump_format(char *buffer, size_t count, struct amdgpu_coredump_inf amdgpu_bo_kunmap(abo); } + amdgpu_bo_unreserve(abo); + output_ib_content: drm_printf(&p, "\nIB #%d 0x%llx %d dw\n", i, coredump->ibs[i].gpu_addr, coredump->ibs[i].ib_size_dw); - for (int j = 0; j < coredump->ibs[i].ib_size_dw; j++) - drm_printf(&p, "0x%08x\n", ib_content[j]); -unreserve_abo: - if (vm) - amdgpu_bo_unreserve(abo); -free_ib_content: + if (!sizing_pass && ib_refs && ib_refs[i].bo) { + for (int j = 0; j < coredump->ibs[i].ib_size_dw; j++) + drm_printf(&p, "0x%08x\n", ib_content[j]); + } kvfree(ib_content); } - if (vm) { - amdgpu_bo_unreserve(root); - amdgpu_bo_unref(&root); - } + + amdgpu_devcoredump_release_ib_refs(ib_refs, coredump->num_ibs); } return count - iter.remain; -- 2.54.0

2 days, 3 hours

Re: [PATCH v2] drm/prime: fix dangling dmabuf entries after handle release

by Christian König

Hi Mingyu, On 5/28/26 15:49, w15303746062 wrote: > Hi Christian, > > Thank you for insisting on this. I've now gone through all callers > of drm_prime_add_buf_handle() in drm_prime.c. > > You are absolutely right: both drm_gem_prime_fd_to_handle() and > drm_gem_prime_handle_to_dmabuf() perform the lookup under > prime_fpriv->lock before adding, so a duplicate handle should indeed > never be inserted through those paths. > > That said, the syzkaller report clearly shows that the dmabufs tree > is not empty when drm_prime_destroy_file_private() runs, which means > some entry wasn't removed. Given that the normal add/remove paths > appear correct, the trigger might be something more subtle — perhaps > a driver-specific callback that bypasses the generic helpers, or an > error path that leaves an orphan in the dmabufs tree. I haven't been > able to identify the exact trigger yet. > > The proposed change to drm_prime_remove_buf_handle() (restart search > instead of break) is intended as a small robustness improvement, not > a fix for a confirmed race. In the normal case it will still execute > only once, but if the trees ever become inconsistent for any reason, > it will clean up all entries for the given handle and prevent the > WARNING. > > Would you be okay with such a defensive approach, or would you prefer > that we first track down the precise trigger (e.g. with additional > WARNs or tracing)? I don't think so. As far as I can see this is not a robustness improvement but just papering over an issue. Leaking memory is usually only a very minor problem, things like use after free or random memory corruption is much more worse. And such things is exactly what starts to happens when you start papering over issues. So I would say find the root cause of what is going on here, you have certainly stumbled over something, and then we can look into how to fix that. But just sending out random patches where a bit of simple code reading can prove them incorrect is not really helpful. Regards, Christian. > > Thanks, > Mingyu

2 days, 3 hours

A Guide to Slither io and the Joy of Simple Gaming

by kaywilson＠wshu.net

In a world filled with hyper-realistic graphics and complex narratives, sometimes the most captivating experiences are the simplest. Enter Slither io, a game that takes the classic "snake" concept and injects it with a healthy dose of online multiplayer mayhem. If you've ever found yourself drawn to the addictive nature of growing a digital creature, or the thrill of outsmarting your opponents in a low-stakes, high-fun environment, then read on. This article will guide you through the basics of Slither io and offer some insights into how to master its charmingly straightforward gameplay. What is Slither io? A Journey into the World of Glowing Serpents Slither io is an online multiplayer arcade game where you control a vibrant, glowing snake. Your objective is deceptively simple: grow your snake by consuming glowing pellets scattered across the map, while avoiding collisions with other players. The twist? Unlike traditional snake games, touching another snake's body (not just its head) means instant demise. This core mechanic creates a dynamic and surprisingly strategic environment where even the smallest snake can take down the largest, given the right timing and tactical positioning. The game's accessibility, with its browser-based play and intuitive controls, makes it a perfect pick-up-and-play experience for anyone looking to unwind and have a little competitive fun. The Dance of the Serpent: Understanding Slither io Gameplay Getting started in Slither io is remarkably easy. Upon loading the game, you'll be prompted to enter a nickname. Once you're in, you'll find yourself as a small, brightly colored snake on a vast, dark arena filled with glowing food. https://slitherio.onl Movement: Your snake follows your mouse cursor. Simply move your mouse to guide your snake in the desired direction. There are no "up, down, left, right" keys – it's all about smooth, continuous movement. Boosting: This is where the strategic element truly shines. By holding down the left mouse button (or spacebar), your snake will accelerate rapidly. While boosting allows you to quickly grab food or outmaneuver opponents, it comes at a cost: your snake will shrink slightly as it consumes a portion of its own mass to fuel the boost. Mastering when and where to boost is crucial for survival and growth. Eating: The primary way to grow your snake is by consuming the colorful pellets scattered across the map. These pellets appear naturally and also drop from deceased snakes. Larger snakes leave behind more food, creating opportunities for smaller snakes to quickly bulk up. Eliminating Opponents: The most satisfying (and often frustrating) part of Slither io is taking down other players. To do this, you need to trick another snake into colliding with your body. There are various tactics, such as circling an opponent, cutting them off, or using a well-timed boost to get in front of their head. When a snake dies, it explodes into a burst of highly nutritious pellets, ready for consumption. Tips for Serpent Supremacy: Mastering the Arena While the gameplay is simple, becoming a truly massive snake requires a blend of patience, observation, and clever tactics. Patience is a Virtue: Don't rush into every engagement. As a small snake, your primary goal is to grow. Focus on consuming loose pellets and avoiding larger players. The Art of the Boost: Use your boost wisely. It's excellent for escaping dangerous situations or quickly grabbing a cluster of food, but over-boosting will shrink you unnecessarily. Learn to anticipate where food will be and use short bursts to get there efficiently. Circle of Life (and Death): Once you've grown to a respectable size, you can start to "circle" smaller snakes. By gradually enclosing them, you force them into a smaller and smaller space until they inevitably collide with your body. Embrace the Edge: The edges of the map can be surprisingly safe, as fewer players tend to congregate there. It’s a good place to grow in relative peace during the early stages of your game. Capitalize on Chaos: When a large snake dies, it creates a feeding frenzy. While it's tempting to dive in immediately, observe the situation. Often, other players will collide in their eagerness, leaving even more food for a patient observer. Don't Be Afraid to Die: Seriously! Each death is a learning opportunity. Pay attention to how you were eliminated and try to avoid making the same mistake twice. The beauty of Slither io is that you can restart instantly and jump back into the action. The Endless Dance: Why Slither io Remains Relevant Slither io, available to play at Slither io, is more than just a casual game; it's a testament to the power of simple yet engaging mechanics. Its low barrier to entry, combined with surprisingly deep strategic possibilities, makes it a timeless classic. Whether you're looking for a quick break, a competitive outlet, or just a chance to unwind, embracing your inner serpent in the vibrant world of Slither io is an experience well worth trying. Go forth, consume, and dominate the leaderboard!

2 days, 3 hours

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig May 2026