From: Michal Hocko <mhocko@kernel.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, kernel-team@lge.com,
Matthew Wilcox <willy@infradead.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] mm: do not access page->mapping directly on page_endio
Date: Fri, 24 Feb 2017 10:13:07 +0100 [thread overview]
Message-ID: <20170224091307.GC19161@dhcp22.suse.cz> (raw)
In-Reply-To: <20170223232609.GA5631@bbox>
On Fri 24-02-17 08:26:09, Minchan Kim wrote:
[...]
> >From 9efb87a873db67a9e6ebf44fdabf7d05fe4b4e21 Mon Sep 17 00:00:00 2001
> From: Minchan Kim <minchan@kernel.org>
> Date: Fri, 4 Nov 2016 09:12:39 +0900
> Subject: [PATCH v2] 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()")
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks for the chagelog update
> ---
> * from v1
> * add more detailed description with Fix tag - Michal
>
> mm/filemap.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/mm/filemap.c b/mm/filemap.c
> index 2ba46f410c7c..1944c631e3e6 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -1008,9 +1008,12 @@ void page_endio(struct page *page, bool is_write, int err)
> unlock_page(page);
> } else {
> if (err) {
> + struct address_space *mapping;
> +
> SetPageError(page);
> - if (page->mapping)
> - mapping_set_error(page->mapping, err);
> + mapping = page_mapping(page);
> + if (mapping)
> + mapping_set_error(mapping, err);
> }
> end_page_writeback(page);
> }
> --
> 2.7.4
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2017-02-24 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 5:39 Minchan Kim
2017-02-22 12:11 ` Michal Hocko
2017-02-22 14:35 ` Minchan Kim
2017-02-22 14:53 ` Michal Hocko
2017-02-23 23:26 ` Minchan Kim
2017-02-24 9:13 ` Michal Hocko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170224091307.GC19161@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome