On Sun, Mar 10, 2024 at 07:59:46PM +0000, Ryan Roberts wrote: > I've now been able to repro this without any of my code on top - just mm-unstable and your fix for the the memcg uncharging ordering issue. So we have separate, more difficultt to repro bug. I've discovered CONFIG_DEBUG_LIST so enabled that. I'll try to bisect in the morning, but I suspect it will be slow going. > > [ 390.317982] ------------[ cut here ]------------ > [ 390.318646] list_del corruption. prev->next should be fffffc00152a9090, but was fffffc002798a490. (prev=fffffc002798a490) Interesting. So prev->next is pointing to prev, ie prev is an empty list, but it should be pointing to this entry ... this is feeling like another missing lock.
