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 14:59:32 +0100 [thread overview]
Message-ID: <20050218135931.GG4056@suse.de> (raw)
In-Reply-To: <20050218125414.GA14362@vienna.egenera.com>
On Fri, Feb 18 2005, Philip R Auld wrote:
> Hi,
> I think there are some potential issues with the reference
> counting of bios as used in 2.6.10. The __make_request function
> which is the default block device routine accesses the bio structure
> after issuing the call to add_request. This means that the bio could
> have completed before __make_request uses it.
>
> The submit_bh path takes an extra reference with an explicit
> bio_get/put pair around the submit_bio, but many other users of
> submit_bio do not. Given that most of the end_io routines remove a
> reference and hence could free the bio this can lead at the least to
> __make_request mis-reading the sync flag. In more extreme cases it can
> cause an oops when run with CONFIG_DEBUG_PAGEALLOC.
>
> The question is what is the preferred fix? I think it may be to simply
> have submit_bio take its own reference (and remove the extra one from
> submit_bh).
>
> Alternatively __make_request could be adjusted so that it does not
> access the bio after calling add_request. All it is doing is checking
> the bi_rw field for the sync bit.
>
> 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.
--
Jens Axboe
next prev parent reply other threads:[~2005-02-18 13:59 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 [this message]
2005-02-18 14:26 ` Philip R Auld
2005-02-18 14:36 ` Jens Axboe
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=20050218135931.GG4056@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