Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1622974

Re: [PATCH] block: bios with an offset are always gappy

From Ming Lei <ming.lei@redhat.com>
Newsgroups linux.kernel
Subject Re: [PATCH] block: bios with an offset are always gappy
Date 2017-04-13 14:20 +0200
Message-ID <tvLTd-2Sx-31@gated-at.bofh.it> (permalink)
References <tvHZf-89-13@gated-at.bofh.it> <tvJRo-1sn-17@gated-at.bofh.it> <tvLzP-2vl-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Thu, Apr 13, 2017 at 01:53:28PM +0200, Johannes Thumshirn wrote:
> On Thu, Apr 13, 2017 at 06:02:21PM +0800, Ming Lei wrote:
> > 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.
> > 
> > Looks I can't reproduce the issue in QEMU(32G nvme, either partitioned
> > or not, just use 'mkfs.btrfs /dev/nvme0n1p1'), could you share the exact
> > mkfs command line and size of your emulated NVMe?
> 
> the exact cmdline is mkfs.btrfs -f /dev/nvme0n1p1 (-f because there was a
> existing btrfs on the image). The image is 17179869184 (a.k.a 16G) bytes.
> 
> [...]
> 
> > Could you try the following patch to see if it fixes your issue?
> 
> It's back to the old, erratic behaviour, see log below.

Ok, could you apply the attached debug patch and collect the
ftrace log? (ftrace_dump_on_oops need to be passed to kernel cmd line).


Thanks,
Ming

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] block: bios with an offset are always gappy Johannes Thumshirn <jthumshirn@suse.de> - 2017-04-13 10:10 +0200
  Re: [PATCH] block: bios with an offset are always gappy Christoph Hellwig <hch@lst.de> - 2017-04-13 11:50 +0200
    Re: [PATCH] block: bios with an offset are always gappy Johannes Thumshirn <jthumshirn@suse.de> - 2017-04-13 12:00 +0200
    Re: [PATCH] block: bios with an offset are always gappy Johannes Thumshirn <jthumshirn@suse.de> - 2017-04-13 12:10 +0200
  Re: [PATCH] block: bios with an offset are always gappy Ming Lei <ming.lei@redhat.com> - 2017-04-13 12:10 +0200
    Re: [PATCH] block: bios with an offset are always gappy Johannes Thumshirn <jthumshirn@suse.de> - 2017-04-13 12:20 +0200
    Re: [PATCH] block: bios with an offset are always gappy Johannes Thumshirn <jthumshirn@suse.de> - 2017-04-13 14:00 +0200
      Re: [PATCH] block: bios with an offset are always gappy Ming Lei <ming.lei@redhat.com> - 2017-04-13 14:20 +0200
        Re: [PATCH] block: bios with an offset are always gappy Ming Lei <ming.lei@redhat.com> - 2017-04-13 15:50 +0200
      Re: [PATCH] block: bios with an offset are always gappy Ming Lei <ming.lei@redhat.com> - 2017-04-13 16:50 +0200
        Re: [PATCH] block: bios with an offset are always gappy Johannes Thumshirn <jthumshirn@suse.de> - 2017-04-13 17:00 +0200
        Re: [PATCH] block: bios with an offset are always gappy Andreas Mohr <andi@lisas.de> - 2017-04-13 22:40 +0200
          Re: [PATCH] block: bios with an offset are always gappy Ming Lei <ming.lei@redhat.com> - 2017-04-14 03:20 +0200

csiph-web