Should fix the recent syzbot report for: https://lore.kernel.org/all/000000000000ee06de0616177560@xxxxxxxxxx/ Patch 1 is a small fixup where I notice mm-unstable crashes with the new hugetlb memcg accounting when testing the changes. Patch 2 should be the fix to the reported issue. Patch 3 is an oneliner to add an assertion similar to what found the issue in patch 2. Only smoke tested over a bunch of hugetlb unit tests. Reviews welcomed. Thanks, Peter Xu (3): fixup! mm: always initialise folio->_deferred_list mm/hugetlb: Fix missing hugetlb_lock for resv uncharge mm/hugetlb: Assert hugetlb_lock in __hugetlb_cgroup_commit_charge mm/hugetlb.c | 5 ++++- mm/hugetlb_cgroup.c | 2 +- mm/memcontrol.c | 1 + 3 files changed, 6 insertions(+), 2 deletions(-) -- 2.44.0
