All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: raid56: fix race between merge_bio and rbio_orig_end_io
Date: Mon, 11 Dec 2017 12:09:46 -0800	[thread overview]
Message-ID: <20171211200945.GA10249@lim.localdomain> (raw)
In-Reply-To: <233e3f98-5f56-c2b8-1aa3-32ea360fe577@suse.com>

On Sat, Dec 09, 2017 at 03:32:18PM +0200, Nikolay Borisov wrote:
> 
> 
> On  9.12.2017 01:02, Liu Bo wrote:
> > We're not allowed to take any new bios to rbio->bio_list in
> > rbio_orig_end_io(), otherwise we may get merged with more bios and
> > rbio->bio_list is not empty.
> > 
> > This should only happens in error-out cases, the normal path of
> > recover and full stripe write have already set RBIO_RMW_LOCKED_BIT to
> > disable merge before doing IO.
> > 
> > Reported-by: Jérôme Carretero <cJ-ko@zougloub.eu>
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> >  fs/btrfs/raid56.c | 13 ++++++++++++-
> >  1 file changed, 12 insertions(+), 1 deletion(-)
> > 
> > diff --git a/fs/btrfs/raid56.c b/fs/btrfs/raid56.c
> > index 5aa9d22..127c782 100644
> > --- a/fs/btrfs/raid56.c
> > +++ b/fs/btrfs/raid56.c
> > @@ -859,12 +859,23 @@ static void free_raid_bio(struct btrfs_raid_bio *rbio)
> >   */
> >  static void rbio_orig_end_io(struct btrfs_raid_bio *rbio, blk_status_t err)
> >  {
> > -	struct bio *cur = bio_list_get(&rbio->bio_list);
> > +	struct bio *cur;
> >  	struct bio *next;
> >  
> > +	/*
> > +	 * We're not allowed to take any new bios to rbio->bio_list
> > +	 * from now on, otherwise we may get merged with more bios and
> > +	 * rbio->bio_list is not empty.
> > +	 */
> > +	spin_lock(&rbio->bio_list_lock);
> > +	set_bit(RBIO_RMW_LOCKED_BIT, &rbio->flags);
> > +	spin_unlock(&rbio->bio_list_lock);
> 
> do we really need the spinlock, bit operations are atomic?
> 

Thanks for the question.

Atomicity doesn't really matter here, set_bit() needs to be done in
the critical section so that merge_rbio() can do right things if
merge_rbio() comes after rbio_orig_end_io().

thanks,
-liubo

> > +
> >  	if (rbio->generic_bio_cnt)
> >  		btrfs_bio_counter_sub(rbio->fs_info, rbio->generic_bio_cnt);
> >  
> > +	cur = bio_list_get(&rbio->bio_list);
> > +
> >  	free_raid_bio(rbio);
> >  
> >  	while (cur) {
> > 

  reply	other threads:[~2017-12-11 20:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 23:02 [PATCH] Btrfs: raid56: fix race between merge_bio and rbio_orig_end_io Liu Bo
2017-12-08 23:05 ` Liu Bo
2017-12-09 13:32 ` Nikolay Borisov
2017-12-11 20:09   ` Liu Bo [this message]
2017-12-12 19:15 ` David Sterba
2018-01-10  1:36 ` [PATCH v2] " Liu Bo

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=20171211200945.GA10249@lim.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.