From: Boaz Harrosh <bharrosh@panasas.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: jens.axboe@oracle.com, linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH] Revert "block: WARN in __blk_put_request() for potential bio leak"
Date: Tue, 09 Jun 2009 14:53:51 +0300 [thread overview]
Message-ID: <4A2E4D4F.90901@panasas.com> (raw)
In-Reply-To: <20090609194338S.fujita.tomonori@lab.ntt.co.jp>
On 06/09/2009 01:44 PM, FUJITA Tomonori wrote:
> This reverts commit 1cd96c242a829d52f7a5ae98f554ca9775429685.
>
> commit 1cd96c242a829d52f7a5ae98f554ca9775429685
> Author: Boaz Harrosh <bharrosh@panasas.com>
> Date: Tue Mar 24 12:35:07 2009 +0100
>
> block: WARN in __blk_put_request() for potential bio leak
>
> Put a WARN_ON in __blk_put_request if it is about to
> leak bio(s). This is a serious bug that can happen in error
> handling code paths.
>
> For this to work I have fixed a couple of places in block/ where
> request->bio != NULL ownership was not honored. And a small cleanup
> at sg_io() while at it.
>
>
> With 2.6.30-rc, BSG SMP requests get the following warnings:
>
> WARNING: at block/blk-core.c:1068 __blk_put_request+0x52/0xc0()
>
> However, this is false. There is no bio leak wrt BSG SMP
> requests. Probably the better fix is calling blk_end_request_all() in
> the BSG SMP path.
>
> blk_end_request_all() is not very useful for the BSG SMP path (we call
> it to just unlink rq->bio) however calling blk_end_request_all() in
> all bio users is consistent.
>
> blk_end_request_all() is not available in 2.6.30-rc so seems that the
> simplest fix is removing WARN_ON for now.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Please do not revert. This is the point of all this.
If there is no leak, You should NULL out the req->bio
for now, and for 2.6.31 change the code to do
blk_end_request_all(). That's what blk_end_request does,
since you are doing your own completion then set req->bio
to null after you're done. (And before put_request)
This stuff is good for error paths to catch leaks, please
leave it?
> ---
> block/blk-core.c | 3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
>
> diff --git a/block/blk-core.c b/block/blk-core.c
> index c89883b..4aacb3c 100644
> --- a/block/blk-core.c
> +++ b/block/blk-core.c
> @@ -1064,9 +1064,6 @@ void __blk_put_request(struct request_queue *q, struct request *req)
>
> elv_completed_request(q, req);
>
> - /* this is a bio leak */
> - WARN_ON(req->bio != NULL);
> -
> /*
> * Request may not have originated from ll_rw_blk. if not,
> * it didn't come out of our reserved rq pools
Please NO
Boaz
next prev parent reply other threads:[~2009-06-09 11:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 10:44 [PATCH] Revert "block: WARN in __blk_put_request() for potential bio leak" FUJITA Tomonori
2009-06-09 11:53 ` Boaz Harrosh [this message]
2009-06-09 13:10 ` FUJITA Tomonori
2009-06-09 13:18 ` Jens Axboe
2009-06-09 13:32 ` Boaz Harrosh
2009-06-09 23:00 ` FUJITA Tomonori
2009-06-10 8:15 ` Boaz Harrosh
2009-06-10 8:29 ` FUJITA Tomonori
2009-06-10 8:34 ` Boaz Harrosh
2009-06-11 10:10 ` FUJITA Tomonori
2009-06-10 8:45 ` Boaz Harrosh
2009-06-10 8:52 ` FUJITA Tomonori
2009-06-10 9:21 ` Boaz Harrosh
2009-06-10 9:36 ` FUJITA Tomonori
2009-06-10 9:48 ` Boaz Harrosh
2009-06-10 10:01 ` FUJITA Tomonori
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=4A2E4D4F.90901@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.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