On Sat, 17 Oct 2026 at 15:45, Greg KH <[email protected]> wrote: > > On Sat, Oct 17, 2026 at 08:19:46AM +1000, Dave Airlie wrote: > > So I got a report that > > > > "the backport of "drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on > > swapout failure" to yesterday's 6.18 missed "drm/ttm: fix swapped-out > > resources never leaving their bulk_move range", > > > > So can we make sure this patch is in the stable branches the other one > > went into? > > Sure, any hint as to what git id that is?
All of the hints: 6.18.57 has commit 060f8f3020516d71bc4d6159d4d0beef85606a74 Author: Thomas Hellström <[email protected]> Date: Tue Apr 28 11:44:42 2026 +0200 drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure [ Upstream commit b2ed01e7ad3de80333e9b962a44024b094bc0b2b ] upstream has two fixes, because we messed up, commit 3db7d7d583419f7b1f2e141e36418802dbb25cf8 Author: Vadim Nikitushkin <[email protected]> Date: Wed Sep 9 23:50:28 2026 +0300 drm/ttm: fix swapped-out resources never leaving their bulk_move range commit fcfe64715b425262af1b36f498f9197f3537ceed Author: Vadim Nikitushkin <[email protected]> Date: Thu Sep 10 17:34:51 2026 +0300 drm/ttm: apply the swapout bulk_move fix to the intended condition we ideally would want the proper resolution of those applied. which is the patch in this thread. So can we just apply the patch in this thread to stable, the squash fixes the stupid in master, or apply both patches to stable and leave the stupid. Dave.
