From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Weijie Yang <weijie.yang.kh@gmail.com>,
Michal Hocko <mhocko@suse.cz>, Shaohua Li <shli@fusionio.com>,
Minchan Kim <minchan@kernel.org>
Subject: Re: [PATCH] swap: fix setting PAGE_SIZE blocksize during swapoff/swapon race
Date: Tue, 15 Oct 2013 13:22:50 +0200 [thread overview]
Message-ID: <1381836170.18389.13.camel@AMDC1943> (raw)
In-Reply-To: <alpine.LNX.2.00.1310150257030.6194@eggly.anvils>
On Tue, 2013-10-15 at 02:59 -0700, Hugh Dickins wrote:
> On Mon, 14 Oct 2013, Krzysztof Kozlowski wrote:
>
> > Fix race between swapoff and swapon resulting in setting blocksize of
> > PAGE_SIZE for block devices during swapoff.
> >
> > The swapon modifies swap_info->old_block_size before acquiring
> > swapon_mutex. It reads block_size of bdev, stores it under
> > swap_info->old_block_size and sets new block_size to PAGE_SIZE.
> >
> > On the other hand the swapoff sets the device's block_size to
> > old_block_size after releasing swapon_mutex.
> >
> > This patch locks the swapon_mutex much earlier during swapon. It also
> > releases the swapon_mutex later during swapoff.
> >
> > The effect of race can be triggered by following scenario:
> > - One block swap device with block size of 512
> > - thread 1: Swapon is called, swap is activated,
> > p->old_block_size = block_size(p->bdev); /512/
> > block_size(p->bdev) = PAGE_SIZE;
> > Thread ends.
> >
> > - thread 2: Swapoff is called and it goes just after releasing the
> > swapon_mutex. The swap is now fully disabled except of setting the
> > block size to old value. The p->bdev->block_size is still equal to
> > PAGE_SIZE.
> >
> > - thread 3: New swapon is called. This swap is disabled so without
> > acquiring the swapon_mutex:
> > - p->old_block_size = block_size(p->bdev); /PAGE_SIZE (!!!)/
> > - block_size(p->bdev) = PAGE_SIZE;
> > Swap is activated and thread ends.
> >
> > - thread 2: resumes work and sets blocksize to old value:
> > - set_blocksize(bdev, p->old_block_size)
> > But now the p->old_block_size is equal to PAGE_SIZE.
> >
> > The patch swap-fix-set_blocksize-race-during-swapon-swapoff does not fix
> > this particular issue. It reduces the possibility of races as the swapon
> > must overwrite p->old_block_size before acquiring swapon_mutex in
> > swapoff.
> >
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>
> Sorry you're being blown back and forth on this, but I say Nack to
> this version. I've not spent the time to check whether it ends up
> correct or not; but your original patch was appropriate to the bug,
> and this one is just unnecessary churn in my view.
Hi,
I still think my previous patch does not solve the issue entirely.
The call set_blocksize() in swapoff quite often sets PAGE_SIZE instead
of valid block size (e.g. 512). I trigger this with:
------
for i in `seq 1000`
do
swapoff /dev/sdc1 &
swapon /dev/sdc1 &
swapon /dev/sdc1 &
done
------
10 seconds run of this script resulted in 50% of set_blocksize(PAGE_SIZE).
Although effect can only be observed after adding printks (block device is
released).
Best regards,
Krzysztof
--
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:[~2013-10-15 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 13:58 [PATCH] swap: fix setting PAGE_SIZE blocksize during swapoff/swapon race Krzysztof Kozlowski
2013-10-15 9:59 ` Hugh Dickins
2013-10-15 11:22 ` Krzysztof Kozlowski [this message]
2013-10-15 17:19 ` Hugh Dickins
2013-10-17 15:48 ` Weijie Yang
2013-10-17 15:59 ` Weijie Yang
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=1381836170.18389.13.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=minchan@kernel.org \
--cc=shli@fusionio.com \
--cc=weijie.yang.kh@gmail.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;
as well as URLs for NNTP newsgroup(s).