[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170413095630.GE6734@linux-x5ow.site>
Date: Thu, 13 Apr 2017 11:56:30 +0200
From: Johannes Thumshirn <jthumshirn@...e.de>
To: Christoph Hellwig <hch@....de>
Cc: Jens Axboe <axboe@...com>, Omar Sandoval <osandov@...ndov.com>,
Ming Lei <ming.lei@...hat.com>,
Bart Van Assche <Bart.VanAssche@...disk.com>,
Hannes Reinecke <hare@...e.de>,
Linux Block Layer Mailinglist <linux-block@...r.kernel.org>,
Linux Kernel Mailinglist <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] block: bios with an offset are always gappy
On Thu, Apr 13, 2017 at 11:48:35AM +0200, Christoph Hellwig wrote:
> 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..
Sure, it's:
mkfs.btrfs, part of btrfs-progs v4.5.3+20160729
Qemu is 2.6.2
[...]
>
> 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).
That's what I tried doing the last two days but as we're rather late in the rc
cycle and it is a regression that came in with -rc1 I'd rather like to have it
fixed or at least have a band aid in place.
Byte,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@...e.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
Powered by blists - more mailing lists