From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Jens Axboe <axboe@fb.com>, Omar Sandoval <osandov@osandov.com>,
Ming Lei <ming.lei@redhat.com>,
Bart Van Assche <Bart.VanAssche@sandisk.com>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
Linux Block Layer Mailinglist <linux-block@vger.kernel.org>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: bios with an offset are always gappy
Date: Thu, 13 Apr 2017 11:48:35 +0200 [thread overview]
Message-ID: <20170413094835.GA28413@lst.de> (raw)
In-Reply-To: <20170413080629.7610-1-jthumshirn@suse.de>
On Thu, Apr 13, 2017 at 10:06:29AM +0200, Johannes Thumshirn wrote:
> Doing a mkfs.btrfs on a (qemu emulated) PCIe NVMe causes a kernel panic
> in nvme_setup_prps() because the dma_len will drop below zero but the
> length not.
I think we should also turns this into a WARN_ON_ONCE + error return..
But do you have an exact btrfsprogs version and command line? I do a lot
of testing that involves mkfs.btrfs on nvme and haven't seen it..
> A git bisect tracked the behaviour down to commit 729204ef49ec ("block:
> relax check on sg gap"). Since commit 729204ef49ec a bio's offsets are not
> taken into account in the decision if the bio will gap any more. Restore
> the old behavior of checking bio offsets as well for the decision if a
> bio will gap.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> Fixes: 729204ef49ec ("block: relax check on sg gap")
> Cc: Ming Lei <ming.lei@redhat.com>
> ---
> include/linux/blkdev.h | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index 7548f332121a..a03b7196209e 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -1677,11 +1677,14 @@ static inline bool bio_will_gap(struct request_queue *q, struct bio *prev,
> {
> if (bio_has_data(prev) && queue_virt_boundary(q)) {
> struct bio_vec pb, nb;
> + bool offset;
>
> bio_get_last_bvec(prev, &pb);
> bio_get_first_bvec(next, &nb);
>
> - if (!bios_segs_mergeable(q, prev, &pb, &nb))
> + offset = pb.bv_offset || nb.bv_offset;
> +
> + if (offset || !bios_segs_mergeable(q, prev, &pb, &nb))
> return __bvec_gap_to_prev(q, &pb, nb.bv_offset);
> }
I think the code in NVMe (and potentially the other drivers using
virt_queue_boundary) is bogus. All of them are actually fine with
gaps in the protocol, as long as the gaps are aligned to said boundary.
So I suspect what we really need is to fix up NVMe, and after that
we could even relax the above check, to not check for offset but
offset & queue_virt_boundary(q).
next prev parent reply other threads:[~2017-04-13 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 8:06 [PATCH] block: bios with an offset are always gappy Johannes Thumshirn
2017-04-13 9:48 ` Christoph Hellwig [this message]
2017-04-13 9:56 ` Johannes Thumshirn
2017-04-13 10:01 ` Johannes Thumshirn
2017-04-13 10:02 ` Ming Lei
2017-04-13 10:10 ` Johannes Thumshirn
2017-04-13 11:53 ` Johannes Thumshirn
2017-04-13 12:11 ` Ming Lei
[not found] ` <20170413122010.GJ6734@linux-x5ow.site>
2017-04-13 13:44 ` Ming Lei
2017-04-13 14:45 ` Ming Lei
2017-04-13 14:50 ` Johannes Thumshirn
2017-04-13 20:35 ` Andreas Mohr
2017-04-14 1:15 ` Ming Lei
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=20170413094835.GA28413@lst.de \
--to=hch@lst.de \
--cc=Bart.VanAssche@sandisk.com \
--cc=axboe@fb.com \
--cc=hare@suse.de \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@osandov.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