From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Minchan Kim <minchan@kernel.org>, Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@techsingularity.net>,
Dave Hansen <dave.hansen@intel.com>,
Chen Liqin <liqin.linux@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
"David S. Miller" <davem@davemloft.net>,
Chris Zankel <chris@zankel.net>,
Vineet Gupta <vgupta@synopsys.com>,
Ley Foon Tan <lftan@altera.com>,
Ralf Baechle <ralf@linux-mips.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH -V2 -mm] mm: Fix races between swapoff and flush dcache
Date: Mon, 5 Mar 2018 10:46:02 +0100 [thread overview]
Message-ID: <20180305094601.GA25231@rapoport-lnx> (raw)
In-Reply-To: <20180305083634.15174-1-ying.huang@intel.com>
On Mon, Mar 05, 2018 at 04:36:34PM +0800, Huang, Ying wrote:
> From: Huang Ying <ying.huang@intel.com>
>
> From commit 4b3ef9daa4fc ("mm/swap: split swap cache into 64MB
> trunks") on, after swapoff, the address_space associated with the swap
> device will be freed. So page_mapping() users which may touch the
> address_space need some kind of mechanism to prevent the address_space
> from being freed during accessing.
>
> The dcache flushing functions (flush_dcache_page(), etc) in
> architecture specific code may access the address_space of swap device
> for anonymous pages in swap cache via page_mapping() function. But in
> some cases there are no mechanisms to prevent the swap device from
> being swapoff, for example,
>
> CPU1 CPU2
> __get_user_pages() swapoff()
> flush_dcache_page()
> mapping = page_mapping()
> ... exit_swap_address_space()
> ... kvfree(spaces)
> mapping_mapped(mapping)
>
> The address space may be accessed after being freed.
>
> But from cachetlb.txt and Russell King, flush_dcache_page() only care
> about file cache pages, for anonymous pages, flush_anon_page() should
> be used. The implementation of flush_dcache_page() in all
> architectures follows this too. They will check whether
> page_mapping() is NULL and whether mapping_mapped() is true to
> determine whether to flush the dcache immediately. And they will use
> interval tree (mapping->i_mmap) to find all user space mappings.
> While mapping_mapped() and mapping->i_mmap isn't used by anonymous
> pages in swap cache at all.
>
> So, to fix the race between swapoff and flush dcache, __page_mapping()
> is add to return the address_space for file cache pages and NULL
> otherwise. All page_mapping() invoking in flush dcache functions are
> replaced with __page_mapping().
>
> Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
> Cc: Minchan Kim <minchan@kernel.org>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Mel Gorman <mgorman@techsingularity.net>
> Cc: Dave Hansen <dave.hansen@intel.com>
> Cc: Chen Liqin <liqin.linux@gmail.com>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
> Cc: "James E.J. Bottomley" <jejb@parisc-linux.org>
> Cc: Guan Xuetao <gxt@mprc.pku.edu.cn>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Chris Zankel <chris@zankel.net>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: Ley Foon Tan <lftan@altera.com>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: Andi Kleen <ak@linux.intel.com>
>
> Changes:
>
> v2:
>
> - Rename __page_mapping() to page_mapping_file() and simplified
> implementation as suggested by Andrew Morton.
> ---
> arch/arc/mm/cache.c | 2 +-
> arch/arm/mm/copypage-v4mc.c | 2 +-
> arch/arm/mm/copypage-v6.c | 2 +-
> arch/arm/mm/copypage-xscale.c | 2 +-
> arch/arm/mm/fault-armv.c | 2 +-
> arch/arm/mm/flush.c | 6 +++---
> arch/mips/mm/cache.c | 2 +-
> arch/nios2/mm/cacheflush.c | 4 ++--
> arch/parisc/kernel/cache.c | 5 +++--
> arch/score/mm/cache.c | 5 +++--
> arch/sh/mm/cache-sh4.c | 2 +-
> arch/sh/mm/cache-sh7705.c | 2 +-
> arch/sparc/kernel/smp_64.c | 8 ++++----
> arch/sparc/mm/init_64.c | 6 +++---
> arch/sparc/mm/tlb.c | 2 +-
> arch/unicore32/mm/flush.c | 2 +-
> arch/unicore32/mm/mmu.c | 2 +-
> arch/xtensa/mm/cache.c | 2 +-
> include/linux/mm.h | 1 +
> mm/util.c | 11 +++++++++++
> 20 files changed, 42 insertions(+), 28 deletions(-)
...
> diff --git a/mm/util.c b/mm/util.c
> index d800ce40816c..252f4748f00b 100644
> --- a/mm/util.c
> +++ b/mm/util.c
> @@ -515,6 +515,17 @@ struct address_space *page_mapping(struct page *page)
> }
> EXPORT_SYMBOL(page_mapping);
>
> +/*
> + * For file cache pages, return the address_space, otherwise return NULL
> + */
> +struct address_space *page_mapping_file(struct page *page)
> +{
> + if (unlikely(PageSwapCache(page)))
> + return NULL;
> + else
Nit: you can drop the 'else' and just fall through to return
page_mapping(page).
> + return page_mapping(page);
> +}
> +
> /* Slow path of page_mapcount() for compound pages */
> int __page_mapcount(struct page *page)
> {
> --
> 2.15.1
>
--
Sincerely yours,
Mike.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-03-05 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 8:36 Huang, Ying
2018-03-05 9:46 ` Mike Rapoport [this message]
2018-03-06 0:47 ` Huang, Ying
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=20180305094601.GA25231@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=dave.hansen@intel.com \
--cc=davem@davemloft.net \
--cc=gxt@mprc.pku.edu.cn \
--cc=hannes@cmpxchg.org \
--cc=jejb@parisc-linux.org \
--cc=lftan@altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=liqin.linux@gmail.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=ralf@linux-mips.org \
--cc=vgupta@synopsys.com \
--cc=ying.huang@intel.com \
--cc=ysato@users.sourceforge.jp \
/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