linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@kernel.org, Dmitry Monakhov <dmonakhov@openvz.org>
Subject: Re: [PATCH v2] block: fix mis-synchronisation in  blkdev_issue_zeroout()
Date: Fri, 11 Mar 2011 15:36:28 +0100	[thread overview]
Message-ID: <4D7A336C.30905@kernel.dk> (raw)
In-Reply-To: <alpine.LFD.2.00.1103111530120.3686@dhcp-27-109.brq.redhat.com>

On 2011-03-11 15:31, Lukas Czerner wrote:
> On Fri, 11 Mar 2011, Jeff Moyer wrote:
> 
>> Lukas Czerner <lczerner@redhat.com> writes:
>>
>>> BZ29402
>>> https://bugzilla.kernel.org/show_bug.cgi?id=29402
>>>
>>> We can hit serious mis-synchronization in bio completion path of
>>> blkdev_issue_zeroout() leading to a panic.
>>>
>>> The problem is that when we are going to wait_for_completion() in
>>> blkdev_issue_zeroout() we check if the bb.done equals issued (number of
>>> submitted bios). If it does, we can skip the wait_for_completition()
>>> and just out of the function since there is nothing to wait for.
>>> However, there is a ordering problem because bio_batch_end_io() is
>>> calling atomic_inc(&bb->done) before complete(), hence it might seem to
>>> blkdev_issue_zeroout() that all bios has been completed and exit. At
>>> this point when bio_batch_end_io() is going to call complete(bb->wait),
>>> bb and wait does not longer exist since it was allocated on stack in
>>> blkdev_issue_zeroout() ==> panic!
>>>
>>> (thread 1)                      (thread 2)
>>> bio_batch_end_io()              blkdev_issue_zeroout()
>>>   if(bb) {                      ...
>>>     if (bb->end_io)             ...
>>>       bb->end_io(bio, err);     ...
>>>     atomic_inc(&bb->done);      ...
>>>     ...                         while (issued != atomic_read(&bb.done))
>>>     ...                         (let issued == bb.done)
>>>     ...                         (do the rest of the function)
>>>     ...                         return ret;
>>>     complete(bb->wait);
>>>     ^^^^^^^^
>>>     panic
>>>
>>> We can fix this easily by simplifying bio_batch and completion counting.
>>>
>>> Also remove bio_end_io_t *end_io since it is not used.
>>>
>>> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
>>> Reported-by: Eric Whitney <eric.whitney@hp.com>
>>> Tested-by: Eric Whitney <eric.whitney@hp.com>
>>> CC: Jens Axboe <axboe@kernel.dk>
>>> CC: Dmitry Monakhov <dmonakhov@openvz.org>
>>> CC: Jeff Moyer <jmoyer@redhat.com>
>>> ---
>>>  block/blk-lib.c |   19 +++++++------------
>>>  1 files changed, 7 insertions(+), 12 deletions(-)
>>>
>>> diff --git a/block/blk-lib.c b/block/blk-lib.c
>>> index eec78be..bd3e8df 100644
>>> --- a/block/blk-lib.c
>>> +++ b/block/blk-lib.c
>>> @@ -109,7 +109,6 @@ struct bio_batch
>>>  	atomic_t 		done;
>>>  	unsigned long 		flags;
>>>  	struct completion 	*wait;
>>> -	bio_end_io_t		*end_io;
>>>  };
>>>  
>>>  static void bio_batch_end_io(struct bio *bio, int err)
>>> @@ -122,12 +121,9 @@ static void bio_batch_end_io(struct bio *bio, int err)
>>>  		else
>>>  			clear_bit(BIO_UPTODATE, &bb->flags);
>>>  	}
>>> -	if (bb) {
>>> -		if (bb->end_io)
>>> -			bb->end_io(bio, err);
>>> -		atomic_inc(&bb->done);
>>> -		complete(bb->wait);
>>> -	}
>>> +	if (bb)
>>> +		if (atomic_dec_and_test(&bb->done))
>>> +			complete(bb->wait);
>>
>> I think bb will always be set here, no real need to check.
>>
>> Anyway, I though I already added my:
>>
>> Reviewed-by: Jeff Moyer <jmoyer@redhat.com>
>>
>> to this.  No?
>>
>> Cheers,
>> Jeff
> 
> Yes, you did and I forgot to add it into the patch. Sorry about that.

No worries, I added it now.

-- 
Jens Axboe

      reply	other threads:[~2011-03-11 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11  8:06 [PATCH v2] block: fix mis-synchronisation in blkdev_issue_zeroout() Lukas Czerner
2011-03-11  9:29 ` Jens Axboe
2011-03-11 14:23 ` Jeff Moyer
2011-03-11 14:31   ` Lukas Czerner
2011-03-11 14:36     ` Jens Axboe [this message]

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=4D7A336C.30905@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=dmonakhov@openvz.org \
    --cc=jmoyer@redhat.com \
    --cc=lczerner@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    /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).