The patch titled
mm/vmscan.c: fix mapping use after free
has been added to the -mm tree. Its filename is
mm-vmscan-fix-mapping-use-after-free.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: mm/vmscan.c: fix mapping use after free
From: Nick Piggin <npiggin@xxxxxxx>
We need lock_page_nosync() here because we have no reference to the
mapping when taking the page lock.
Signed-off-by: Nick Piggin <npiggin@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/vmscan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/vmscan.c~mm-vmscan-fix-mapping-use-after-free mm/vmscan.c
--- a/mm/vmscan.c~mm-vmscan-fix-mapping-use-after-free
+++ a/mm/vmscan.c
@@ -296,7 +296,7 @@ static int may_write_to_queue(struct bac
static void handle_write_error(struct address_space *mapping,
struct page *page, int error)
{
- lock_page(page);
+ lock_page_nosync(page);
if (page_mapping(page) == mapping)
mapping_set_error(mapping, error);
unlock_page(page);
_
Patches currently in -mm which might be from npiggin@xxxxxxx are
linux-next.patch
avr32-invoke-oom-killer-from-page-fault.patch
mm-vmscan-fix-mapping-use-after-free.patch
fs-move-code-out-of-bufferc.patch
mm-vmap-area-cache.patch
mm-vmap-area-cache-fix.patch
oom-filter-tasks-not-sharing-the-same-cpuset.patch
oom-sacrifice-child-with-highest-badness-score-for-parent.patch
oom-remove-special-handling-for-pagefault-ooms.patch
reiser4.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
