From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [BUGFIX][1/2] mm: add_to_swap_cache() must not sleep
Date: Mon, 10 Aug 2009 12:16:44 +0900 [thread overview]
Message-ID: <20090810121644.6fe466f9.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090810112641.02e1db72.nishimura@mxp.nes.nec.co.jp>
On Mon, 10 Aug 2009 11:26:41 +0900
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> After commit 355cfa73(mm: modify swap_map and add SWAP_HAS_CACHE flag),
> read_swap_cache_async() will busy-wait while a entry doesn't on swap cache
> but it has SWAP_HAS_CACHE flag.
>
> Such entries can exist on add/delete path of swap cache.
> On add path, add_to_swap_cache() is called soon after SWAP_HAS_CACHE flag
> is set, and on delete path, swapcache_free() will be called (SWAP_HAS_CACHE
> flag is cleared) soon after __delete_from_swap_cache() is called.
> So, the busy-wait works well in most cases.
>
yes.
> But this mechanism can cause soft lockup if add_to_swap_cache() sleeps
> and read_swap_cache_async() tries to swap-in the same entry on the same cpu.
>
Hmm..
> add_to_swap() and shmem_writepage() call add_to_swap_cache() w/o __GFP_WAIT,
> but read_swap_cache_async() can call it w/ __GFP_WAIT, so it can cause
> soft lockup.
>
> This patch changes the gfp_mask of add_to_swap_cache() in read_swap_cache_async().
>
> Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Thank you for catching.
Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
But Hm...I wonder whether this is the best fix.
If I was you, I may do following.
1. remove radix_tree_preload() and gfp_mask from add_to_swapcache().
Then, rename it fo __add_to_swapcache().
Or, move swap_duplicate() into add_to_swapcache() with a new flag.
2. do things in following order.
radix_tree_peload();
swap_duplicate(); # this never sleeps.
add_to_swapcache()
radix_tree_peload_end();
Good point of this approach is
- we can use __GFP_WAIT in gfp_mask.
- -ENOMEM means OOM, then, we should be aggressive to get a page.
How do you think ?
Thanks,
-Kame
> ---
> mm/swap_state.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/mm/swap_state.c b/mm/swap_state.c
> index 42cd38e..3e6dd72 100644
> --- a/mm/swap_state.c
> +++ b/mm/swap_state.c
> @@ -76,6 +76,7 @@ int add_to_swap_cache(struct page *page, swp_entry_t entry, gfp_t gfp_mask)
> VM_BUG_ON(!PageLocked(page));
> VM_BUG_ON(PageSwapCache(page));
> VM_BUG_ON(!PageSwapBacked(page));
> + VM_BUG_ON(gfp_mask & __GFP_WAIT);
>
> error = radix_tree_preload(gfp_mask);
> if (!error) {
> @@ -307,7 +308,7 @@ struct page *read_swap_cache_async(swp_entry_t entry, gfp_t gfp_mask,
> */
> __set_page_locked(new_page);
> SetPageSwapBacked(new_page);
> - err = add_to_swap_cache(new_page, entry, gfp_mask & GFP_KERNEL);
> + err = add_to_swap_cache(new_page, entry, GFP_ATOMIC);
> if (likely(!err)) {
> /*
> * Initiate read into locked page and return.
>
--
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:[~2009-08-10 3:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 2:23 [RFC][PATCH 0/2] mm: some patches about add_to_swap_cache() Daisuke Nishimura
2009-08-10 2:26 ` [BUGFIX][1/2] mm: add_to_swap_cache() must not sleep Daisuke Nishimura
2009-08-10 3:16 ` KAMEZAWA Hiroyuki [this message]
2009-08-10 5:49 ` Daisuke Nishimura
2009-08-10 5:58 ` KAMEZAWA Hiroyuki
2009-08-10 2:27 ` [cleanup][2/2] mm: add_to_swap_cache() does not return -EEXIST Daisuke Nishimura
2009-08-10 3:19 ` KAMEZAWA Hiroyuki
2009-08-14 6:16 ` Daisuke Nishimura
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=20090810121644.6fe466f9.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.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