On Sat, Mar 22, 2025 at 07:14:40PM -0400, Johannes Weiner wrote: > Hey Luis, > > This looks like the same issue the bot reported here: > > https://lore.kernel.org/all/20250321135524.GA1888695@xxxxxxxxxxx/ > > There is a fix for it queued in next-20250318 and later. Could you > please double check with your reproducer against a more recent next? Confirmed, at least it's been 30 minutes and no crashes now where as before it would crash in 1 minute. I'll let it soak for 2.5 hours in the hopes I can trigger the warning originally reported by this thread. Even though from code inspection I see how the kernel warning would trigger I just want to force trigger it on a test, and I can't yet. Luis
