From: Andrew Morton <akpm@linux-foundation.org>
To: Weijie Yang <weijie.yang.kh@gmail.com>
Cc: Weijie Yang <weijie.yang@samsung.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>, Hugh Dickins <hughd@google.com>,
Minchan Kim <minchan@kernel.org>, Shaohua Li <shli@fusionio.com>,
Bob Liu <bob.liu@oracle.com>,
stable@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>
Subject: Re: [PATCH] mm/swap: fix race on swap_info reuse between swapoff and swapon
Date: Sun, 12 Jan 2014 19:27:44 -0800 [thread overview]
Message-ID: <20140112192744.9bca5c6d.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAL1ERfPnaROPiRAeWHpvwGezHsqN4R8j=QSyS48xs25ax14AhA@mail.gmail.com>
On Mon, 13 Jan 2014 11:08:58 +0800 Weijie Yang <weijie.yang.kh@gmail.com> wrote:
> >> --- a/mm/swapfile.c
> >> +++ b/mm/swapfile.c
> >> @@ -1922,7 +1922,6 @@ SYSCALL_DEFINE1(swapoff, const char __user *, specialfile)
> >> p->swap_map = NULL;
> >> cluster_info = p->cluster_info;
> >> p->cluster_info = NULL;
> >> - p->flags = 0;
> >> frontswap_map = frontswap_map_get(p);
> >> spin_unlock(&p->lock);
> >> spin_unlock(&swap_lock);
> >> @@ -1948,6 +1947,16 @@ SYSCALL_DEFINE1(swapoff, const char __user *, specialfile)
> >> mutex_unlock(&inode->i_mutex);
> >> }
> >> filp_close(swap_file, NULL);
> >> +
> >> + /*
> >> + * clear SWP_USED flag after all resources freed
> >> + * so that swapon can reuse this swap_info in alloc_swap_info() safely
> >> + * it is ok to not hold p->lock after we cleared its SWP_WRITEOK
> >> + */
> >> + spin_lock(&swap_lock);
> >> + p->flags = 0;
> >> + spin_unlock(&swap_lock);
> >> +
> >> err = 0;
> >> atomic_inc(&proc_poll_event);
> >> wake_up_interruptible(&proc_poll_wait);
> >
> > I didn't look too closely, but this patch might also address the race
> > which Krzysztof addressed with
> > http://ozlabs.org/~akpm/mmots/broken-out/swap-fix-setting-page_size-blocksize-during-swapoff-swapon-race.patch.
> > Can we please check that out?
> >
> > I do prefer fixing all these swapon-vs-swapoff races with some large,
> > simple, wide-scope exclusion scheme. Perhaps SWP_USED is that scheme.
> >
> > An alternative would be to add another mutex and just make sys_swapon()
> > and sys_swapoff() 100% exclusive. But that is plastering yet another
> > lock over this mess to hide the horrors which lurk within :(
> >
>
> Hi, Andrew. Thanks for your suggestion.
>
> I checked Krzysztof's patch, it use the global swapon_mutex to protect
> race condition among
> swapon, swapoff and swap_start(). It is a kind of correct method, but
> a heavy method.
But do you agree that your
http://ozlabs.org/~akpm/mmots/broken-out/mm-swap-fix-race-on-swap_info-reuse-between-swapoff-and-swapon.patch
makes Krzysztof's
http://ozlabs.org/~akpm/mmots/broken-out/swap-fix-setting-page_size-blocksize-during-swapoff-swapon-race.patch
obsolete?
I've been sitting on Krzysztof's
swap-fix-setting-page_size-blocksize-during-swapoff-swapon-race.patch
for several months - Hugh had issues with it so I put it on hold and
nothing further happened.
> I will try to resend a patchset to make lock usage in swapfile.c clear
> and fine grit
OK, thanks. In the meanwhile I'm planning on dropping Krzysztof's
patch and merging your patch into 3.14-rc1, which is why I'd like
confirmation that your patch addresses the issues which Krzysztof
identified?
--
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:[~2014-01-13 3:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 5:39 Weijie Yang
2014-01-11 0:38 ` Andrew Morton
2014-01-11 1:11 ` Andrew Morton
2014-01-13 3:08 ` Weijie Yang
2014-01-13 3:27 ` Andrew Morton [this message]
2014-01-13 3:51 ` Weijie Yang
2014-01-13 6:27 ` Mateusz Guzik
2014-01-13 7:36 ` Weijie Yang
2014-02-01 2:49 ` Hugh Dickins
2014-02-01 2:07 ` Hugh Dickins
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=20140112192744.9bca5c6d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=hughd@google.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=shli@fusionio.com \
--cc=stable@vger.kernel.org \
--cc=weijie.yang.kh@gmail.com \
--cc=weijie.yang@samsung.com \
/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