From: Ming Lei <ming.lei@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Mason <clm@fb.com>
Subject: Re: [PATCH] block: fix splitting segments
Date: Tue, 7 Jan 2020 23:23:39 +0800 [thread overview]
Message-ID: <20200107152339.GA23622@ming.t460p> (raw)
In-Reply-To: <20200107124708.GA20285@roeck-us.net>
On Tue, Jan 07, 2020 at 04:47:08AM -0800, Guenter Roeck wrote:
> Hi,
>
> On Sun, Dec 29, 2019 at 10:32:30AM +0800, Ming Lei wrote:
> > There are two issues in get_max_segment_size():
> >
> > 1) the default segment boudary mask is bypassed, and some devices still
> > require segment to not cross the default 4G boundary
> >
> > 2) the segment start address isn't taken into account when checking
> > segment boundary limit
> >
> > Fixes the two issues.
> >
> > Fixes: dcebd755926b ("block: use bio_for_each_bvec() to compute multi-page bvec count")
> > Signed-off-by: Ming Lei <ming.lei@redhat.com>
>
> This patch, pushed into mainline as "block: fix splitting segments on
> boundary masks", results in the following crash when booting 'versatilepb'
> in qemu from disk. Bisect log is attached. Detailed log is at
> https://kerneltests.org/builders/qemu-arm-master/builds/1410/steps/qemubuildcommand/logs/stdio
>
> Guenter
>
> ---
> Crash:
>
> kernel BUG at block/bio.c:1885!
> Internal error: Oops - BUG: 0 [#1] ARM
Please apply the following debug patch, and post the log.
diff --git a/block/blk-merge.c b/block/blk-merge.c
index 347782a24a35..c4aa683a1c20 100644
--- a/block/blk-merge.c
+++ b/block/blk-merge.c
@@ -217,6 +217,33 @@ static bool bvec_split_segs(const struct request_queue *q,
return len > 0 || bv->bv_len > max_len;
}
+static void blk_dump_bio(struct request_queue *q, struct bio *bio,
+ unsigned secs)
+{
+ struct bvec_iter iter;
+ struct bio_vec bvec;
+ int i = 0;
+ unsigned sectors = 0;
+
+ printk("max_sectors %u max_segs %u max_seg_size %u mask %lx\n",
+ get_max_io_size(q, bio), queue_max_segments(q),
+ queue_max_segment_size(q), queue_segment_boundary(q));
+ printk("%p: %hx/%hx %llu %u, %u\n",
+ bio,
+ bio->bi_flags, bio->bi_opf,
+ (unsigned long long)bio->bi_iter.bi_sector,
+ bio->bi_iter.bi_size, secs);
+ bio_for_each_bvec(bvec, bio, iter) {
+ sectors += bvec.bv_len >> 9;
+ trace_printk("\t %d: %lu %u %u(%u)\n", i++,
+ (unsigned long)page_to_pfn(bvec.bv_page),
+ bvec.bv_offset,
+ bvec.bv_len, bvec.bv_len >> 12);
+ }
+ printk("\t total sectors %u\n", sectors);
+}
+
+
/**
* blk_bio_segment_split - split a bio in two bios
* @q: [in] request queue pointer
@@ -273,6 +300,9 @@ static struct bio *blk_bio_segment_split(struct request_queue *q,
return NULL;
split:
*segs = nsegs;
+
+ if (sectors <= 0 || sectors >= bio_sectors(bio))
+ blk_dump_bio(q, bio, sectors);
return bio_split(bio, sectors, GFP_NOIO, bs);
}
Thanks,
Ming
next prev parent reply other threads:[~2020-01-07 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191229023230.28940-1-ming.lei@redhat.com>
2020-01-07 12:47 ` [PATCH] block: fix splitting segments Guenter Roeck
2020-01-07 15:23 ` Ming Lei [this message]
2020-01-07 18:11 ` Guenter Roeck
2020-01-07 22:30 ` Ming Lei
2020-01-07 22:32 ` Jens Axboe
2020-01-08 1:59 ` Ming Lei
2020-01-08 2:36 ` Jens Axboe
2020-01-07 23:06 ` Guenter Roeck
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=20200107152339.GA23622@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=clm@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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