From: Namhyung Kim <namhyung@kernel.org>
To: NeilBrown <neilb@suse.de>
Cc: Jens Axboe <axboe@kernel.dk>, Shaohua Li <shli@fusionio.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: makes bio_split support bio without data
Date: Mon, 24 Sep 2012 17:35:34 +0900 [thread overview]
Message-ID: <87txunyg15.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20120924145639.3b65fd8b@notabene.brown> (NeilBrown's message of "Mon, 24 Sep 2012 14:56:39 +1000")
Hi,
On Mon, 24 Sep 2012 14:56:39 +1000, NeilBrown wrote:
> Hi Jens,
> this patch has been sitting in my -next tree for a little while and I was
> hoping for it to go in for the next merge window.
> It simply allows bio_split() to be used on bios without a payload, such as
> 'discard'.
> Are you happy with it going in though my 'md' tree, or would you rather take
> it though your 'block' tree?
>
> Thanks,
> NeilBrown
>
>
> From: Shaohua Li <shli@fusionio.com>
> Date: Thu, 20 Sep 2012 09:36:03 +1000
> Subject: [PATCH] block: makes bio_split support bio without data
>
> discard bio hasn't data attached. We hit a BUG_ON with such bio. This makes
> bio_split works for such bio.
>
> Signed-off-by: Shaohua Li <shli@fusionio.com>
> Signed-off-by: NeilBrown <neilb@suse.de>
>
> diff --git a/fs/bio.c b/fs/bio.c
> index 71072ab..dbb7a6c 100644
> --- a/fs/bio.c
> +++ b/fs/bio.c
> @@ -1501,7 +1501,7 @@ struct bio_pair *bio_split(struct bio *bi, int first_sectors)
> trace_block_split(bdev_get_queue(bi->bi_bdev), bi,
> bi->bi_sector + first_sectors);
>
> - BUG_ON(bi->bi_vcnt != 1);
> + BUG_ON(bi->bi_vcnt != 1 && bi->bi_vcnt != 0);
Why not
BUG_ON(bi->bi_vcnt > 1);
?
Thanks,
Namhyung
> BUG_ON(bi->bi_idx != 0);
> atomic_set(&bp->cnt, 3);
> bp->error = 0;
> @@ -1511,17 +1511,19 @@ struct bio_pair *bio_split(struct bio *bi, int first_sectors)
> bp->bio2.bi_size -= first_sectors << 9;
> bp->bio1.bi_size = first_sectors << 9;
>
> - bp->bv1 = bi->bi_io_vec[0];
> - bp->bv2 = bi->bi_io_vec[0];
> - bp->bv2.bv_offset += first_sectors << 9;
> - bp->bv2.bv_len -= first_sectors << 9;
> - bp->bv1.bv_len = first_sectors << 9;
> + if (bi->bi_vcnt != 0) {
> + bp->bv1 = bi->bi_io_vec[0];
> + bp->bv2 = bi->bi_io_vec[0];
> + bp->bv2.bv_offset += first_sectors << 9;
> + bp->bv2.bv_len -= first_sectors << 9;
> + bp->bv1.bv_len = first_sectors << 9;
>
> - bp->bio1.bi_io_vec = &bp->bv1;
> - bp->bio2.bi_io_vec = &bp->bv2;
> + bp->bio1.bi_io_vec = &bp->bv1;
> + bp->bio2.bi_io_vec = &bp->bv2;
>
> - bp->bio1.bi_max_vecs = 1;
> - bp->bio2.bi_max_vecs = 1;
> + bp->bio1.bi_max_vecs = 1;
> + bp->bio2.bi_max_vecs = 1;
> + }
>
> bp->bio1.bi_end_io = bio_pair_end_1;
> bp->bio2.bi_end_io = bio_pair_end_2;
next prev parent reply other threads:[~2012-09-24 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 4:56 NeilBrown
2012-09-24 8:35 ` Namhyung Kim [this message]
2012-09-24 23:37 ` NeilBrown
2012-09-25 12:51 ` Jens Axboe
2012-09-28 7:36 ` Shaohua Li
2012-09-28 8:39 ` Jens Axboe
2012-09-28 16:23 ` Kent Overstreet
2012-10-02 6:22 ` NeilBrown
2012-10-02 21:09 ` Kent Overstreet
2012-10-03 3:30 ` NeilBrown
2012-10-03 3:42 ` Kent Overstreet
2012-10-03 16:22 ` Martin K. Petersen
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=87txunyg15.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=shli@fusionio.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
Powered by JetHome