mm: Two small fixes for recent syzbot reports
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 53 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm/mempolicy: Allow lookup_node() to handle fatal signalmm/ | +5 | 16 replies | |
| 2/2 | mm/gup: Mark lock taken only after a successful retakemm/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] mm: Two small fixes for recent syzbot reports
The two patches should fix below syzbot reports:
BUG: unable to handle kernel paging request in kernel_get_mempolicy https://lore.kernel.org/lkml/[email protected]/
WARNING: bad unlock balance in __get_user_pages_remote
https://lore.kernel.org/lkml/[email protected]/
Note that the 1st patch also applied two extra small changes comparing to when posted on the list in that: (1) it squashed an "interupt" spelling error that Andrew has pointed out when picked up, and (2) it also initializes the "page" pointer to NULL. But I'm fairly confident it shouldn't affect the correctness of the patch.
The 2nd patch is exactly the patch posted previously.
Thanks,
Peter Xu (2):
mm/mempolicy: Allow lookup_node() to handle fatal signal mm/gup: Mark lock taken only after a successful retake
mm/gup.c | 2 +- mm/mempolicy.c | 7 +++++-- 2 files changed, 6 insertions(+), 3 deletions(-)
Signature · 1 line
2.24.1