From: Keith Busch <kbusch@kernel.org>
To: Ben Copeland <ben.copeland@linaro.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, lkft-triage@lists.linaro.org,
regressions@lists.linux.dev, linux-nvme@lists.infradead.org,
Dan Carpenter <dan.carpenter@linaro.org>,
axboe@kernel.dk, sagi@grimberg.me, iommu@lists.linux.dev
Subject: Re: next-20250627: IOMMU DMA warning during NVMe I/O completion after 06cae0e3f61c
Date: Tue, 1 Jul 2025 10:20:41 -0400 [thread overview]
Message-ID: <aGPuue3_-BSPffR0@kbusch-mbp> (raw)
In-Reply-To: <CAL0q8a7acv-9N1XUmJ9LAojdhm947eiira6Kx0tew-VVVCY6kg@mail.gmail.com>
On Tue, Jul 01, 2025 at 02:05:04PM +0100, Ben Copeland wrote:
> Even though SGLs are not supported, I gave you the patch a spin and
> saw the same stack traces.
Right, that patch applies only if SGL is not supported, but it's only
fixing part of the problem, so I expected it would still fail.
The dma teardown needs to be symetric to the dma mapping, but we've
removed the sg-table now, so we don't have the original mapping context
in the completion path here. Christoph replied with a patch that tries
to infer it based on the dma_addr continuity, which I think should work
for you, but I'll have to look a bit closer to be confident it's always
the correct assumption.
next prev parent reply other threads:[~2025-07-01 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250630075218epcas5p1f3d467fffa468cac0ccd012c193e94df@epcas5p1.samsung.com>
2025-06-30 7:50 ` next-20250627: IOMMU DMA warning during NVMe I/O completion after 06cae0e3f61c Ben Copeland
2025-06-30 13:33 ` Christoph Hellwig
2025-06-30 19:51 ` Ben Copeland
2025-07-01 19:43 ` Keith Busch
2025-06-30 20:25 ` Keith Busch
2025-07-01 0:54 ` Keith Busch
2025-07-01 13:05 ` Ben Copeland
2025-07-01 14:20 ` Keith Busch [this message]
2025-07-01 13:29 ` Christoph Hellwig
2025-07-01 15:58 ` Leon Romanovsky
2025-07-01 21:00 ` Keith Busch
2025-07-03 9:30 ` Christoph Hellwig
2025-07-03 14:29 ` Keith Busch
2025-07-03 15:13 ` Ben Copeland
2025-07-03 5:54 ` Kanchan Joshi
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=aGPuue3_-BSPffR0@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=ben.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkft-triage@lists.linaro.org \
--cc=regressions@lists.linux.dev \
--cc=sagi@grimberg.me \
/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