All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: kernel BUG at nvme/host/pci.c
Date: Sat, 15 Jul 2017 01:51:41 -0700	[thread overview]
Message-ID: <20170715085141.GC25753@infradead.org> (raw)
In-Reply-To: <20170714170846.GA24365@localhost.localdomain>

On Fri, Jul 14, 2017@01:08:47PM -0400, Keith Busch wrote:
> > So LVM2 backed by md raid1 isn't compatible with newer hardware... Any
> > suggestions?
> 
> It's not that LVM2 or RAID isn't compatible. Either the IOMMU isn't
> compatible if can use different page offsets for DMA addresses than the
> physical aaddresses, or the driver for it is broken. The DMA addresses
> in this mapped SGL look completely broken, at least, since the last 4
> entries are all the same address. That'll corrupt data.

Given that this is a Xen system I wonder if swiotlb-xen is involved
here, which does some odd chunking of dma translations?

> 
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
---end quoted text---

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Keith Busch <keith.busch@intel.com>
Cc: xen-devel@lists.xenproject.org,
	Andreas Pflug <pgadmin@pse-consulting.de>,
	linux-nvme@lists.infradead.org
Subject: Re: kernel BUG at nvme/host/pci.c
Date: Sat, 15 Jul 2017 01:51:41 -0700	[thread overview]
Message-ID: <20170715085141.GC25753@infradead.org> (raw)
In-Reply-To: <20170714170846.GA24365@localhost.localdomain>

On Fri, Jul 14, 2017 at 01:08:47PM -0400, Keith Busch wrote:
> > So LVM2 backed by md raid1 isn't compatible with newer hardware... Any
> > suggestions?
> 
> It's not that LVM2 or RAID isn't compatible. Either the IOMMU isn't
> compatible if can use different page offsets for DMA addresses than the
> physical aaddresses, or the driver for it is broken. The DMA addresses
> in this mapped SGL look completely broken, at least, since the last 4
> entries are all the same address. That'll corrupt data.

Given that this is a Xen system I wonder if swiotlb-xen is involved
here, which does some odd chunking of dma translations?

> 
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
---end quoted text---

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-07-15  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 18:03 kernel BUG at nvme/host/pci.c Andreas Pflug
2017-07-10 19:08 ` Keith Busch
2017-07-11  7:44   ` Andreas Pflug
2017-07-11 19:45     ` Keith Busch
2017-07-11 19:44       ` Scott Bauer
2017-07-12  6:06       ` Andreas Pflug
2017-07-12 19:50         ` Keith Busch
2017-07-13  8:46           ` Andreas Pflug
2017-07-13  9:00             ` Sagi Grimberg
2017-07-13 13:47             ` Keith Busch
2017-07-14 16:47               ` Andreas Pflug
2017-07-14 17:08                 ` Keith Busch
2017-07-15  8:51                   ` Christoph Hellwig [this message]
2017-07-15  8:51                     ` Christoph Hellwig
2017-07-15 13:34                     ` Andreas Pflug
2017-07-15 13:34                       ` Andreas Pflug

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=20170715085141.GC25753@infradead.org \
    --to=hch@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.