From: Jens Axboe <axboe@suse.de>
To: Philip R Auld <pauld@egenera.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bio refcount problem
Date: Fri, 18 Feb 2005 15:36:04 +0100 [thread overview]
Message-ID: <20050218143603.GA16511@suse.de> (raw)
In-Reply-To: <20050218142607.GB14362@vienna.egenera.com>
On Fri, Feb 18 2005, Philip R Auld wrote:
> Hi,
>
> Rumor has it that on Fri, Feb 18, 2005 at 02:59:32PM +0100 Jens Axboe said:
> > On Fri, Feb 18 2005, Philip R Auld wrote:
>
> ...
> > > Or make all users of submit_bio take and release and extra reference
> > > like submit_bh.
> >
> > The queue lock is still held at that point, so the driver hasn't had a
> > chance to process the request yet.
>
> Interesting. This is not a theoretical problem though. I've got traces of
> the oops showing the bio getting freed before the bio_sync(bio) test.
> When you say driver here what level do you mean? scsi_request_fn at
> least drops the queue lock.
But it must be holding the lock to retrieve the request in question, so
there should be no opening for a completion race there.
> What if it's merged instead of added directly? That could also get to
> the same place.
Same deal - if the request is already seen by the driver, merging is not
allowed. If not, then the same rules apply.
> The end_io callback _is_ getting called before __make_request
> does its "if(bio_sync(bio))" test.
Sounds strange, it sounds like a driver issue. If you have time, please
do poke some more at this. I'll try to be responsive, but I'm busy with
other things atm. Are you using a vanilla kernel?
--
Jens Axboe
prev parent reply other threads:[~2005-02-18 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 12:54 bio refcount problem Philip R Auld
2005-02-18 13:59 ` Jens Axboe
2005-02-18 14:26 ` Philip R Auld
2005-02-18 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=20050218143603.GA16511@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pauld@egenera.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