From: Kanchan Joshi <joshi.k@samsung.com>
To: Ben Copeland <ben.copeland@linaro.org>,
linux-kernel@vger.kernel.org, lkft-triage@lists.linaro.org,
regressions@lists.linux.dev, linux-nvme@lists.infradead.org
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me
Subject: Re: next-20250627: IOMMU DMA warning during NVMe I/O completion after 06cae0e3f61c
Date: Thu, 3 Jul 2025 11:24:20 +0530 [thread overview]
Message-ID: <07c07d1f-2eb6-437f-931c-0f04b129eb08@samsung.com> (raw)
In-Reply-To: <CAL0q8a6pOBZbWYdwKzC1U-PuH4rgf2miv0jcF=fWVZt_dUZHmw@mail.gmail.com>
On 6/30/2025 1:20 PM, Ben Copeland wrote:
> # first bad commit: [06cae0e3f61c4c1ef18726b817bbb88c29f81e57]
> nvme-pci: merge the simple PRP and SGL setup into a common helper
this patch had the problem [0] of not setting 'iod->first_dma' which can
trigger that IOMMU warning on unmap.
But problem was transient as a subsequent patch removed the
iod->first_dma and made unmapping work without that.
[0]
-static blk_status_t nvme_setup_prp_simple(struct nvme_dev *dev,
- struct request *req, struct nvme_rw_command *cmnd,
- struct bio_vec *bv)
+static blk_status_t nvme_pci_setup_data_simple(struct request *req,
+ enum nvme_use_sgl use_sgl)
{
struct nvme_iod *iod = blk_mq_rq_to_pdu(req);
- unsigned int offset = bv->bv_offset & (NVME_CTRL_PAGE_SIZE - 1);
- unsigned int first_prp_len = NVME_CTRL_PAGE_SIZE - offset;
-
- iod->first_dma = dma_map_bvec(dev->dev, bv, rq_dma_dir(req), 0);
- if (dma_mapping_error(dev->dev, iod->first_dma))
iod->first_dma does not get set, and that can cause unmap on invalid
address during teardown.
prev parent reply other threads:[~2025-07-03 6:03 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 ` 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
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 [this message]
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=07c07d1f-2eb6-437f-931c-0f04b129eb08@samsung.com \
--to=joshi.k@samsung.com \
--cc=axboe@kernel.dk \
--cc=ben.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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
all inboxes | Powered by JetHome®