diff options
author | Minchan Kim <minchan@kernel.org> | 2017-02-24 14:59:59 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-02-24 17:46:56 -0800 |
commit | dd8416c47715cf324c9a16f13273f9fda87acfed (patch) | |
tree | cc5242e75522222820fc691368dc9357b20ae50c /lib/ioremap.c | |
parent | 9a8b300f2f7812ebf4630b8b40499da38b38e882 (diff) | |
download | linux-stable-dd8416c47715cf324c9a16f13273f9fda87acfed.tar.gz linux-stable-dd8416c47715cf324c9a16f13273f9fda87acfed.tar.bz2 linux-stable-dd8416c47715cf324c9a16f13273f9fda87acfed.zip |
mm: do not access page->mapping directly on page_endio
With rw_page, page_endio is used for completing IO on a page and it
propagates write error to the address space if the IO fails. The
problem is it accesses page->mapping directly which might be okay for
file-backed pages but it shouldn't for anonymous page. Otherwise, it
can corrupt one of field from anon_vma under us and system goes panic
randomly.
swap_writepage
bdev_writepage
ops->rw_page
I encountered the BUG during developing new zram feature and it was
really hard to figure it out because it made random crash, somtime
mmap_sem lockdep, sometime other places where places never related to
zram/zsmalloc, and not reproducible with some configuration.
When I consider how that bug is subtle and people do fast-swap test with
brd, it's worth to add stable mark, I think.
Fixes: dd6bd0d9c7db ("swap: use bdev_read_page() / bdev_write_page()")
Signed-off-by: Minchan Kim <minchan@kernel.org>
Acked-by: Michal Hocko <mhocko@suse.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/ioremap.c')
0 files changed, 0 insertions, 0 deletions