mm/hugetlb: Fix missing hugetlb_lock for memcg resv uncharge
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 5 repliesIn review 2 of 3 applied
Patches in v1 2 of 3 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | fixup! mm: always initialise folio->_deferred_listmm/ | +1 | 2 replies | |
| 2/3 | mm/hugetlb: Fix missing hugetlb_lock for resv unchargemm/ | +4 | 1 reply | Applied |
| 3/3 | mm/hugetlb: Assert hugetlb_lock in __hugetlb_cgroup_commit_chargemm/ | +1 | 2 replies | Applied |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Mina Almasry |
|---|---|
| 1/3 | |
| 2/3 | R-b |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] mm/hugetlb: Fix missing hugetlb_lock for memcg resv uncharge
Should fix the recent syzbot report for:
https://lore.kernel.org/all/[email protected]/
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(-)
Signature · 1 line
2.44.0