From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
kbusch@kernel.org, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Klara Modin <klarasmodin@gmail.com>
Subject: Re: [PATCH] nvme-pci: don't allocate dma_vec for IOVA mappings
Date: Mon, 14 Jul 2025 13:42:13 +0200 [thread overview]
Message-ID: <20250714114213.GA1998@lst.de> (raw)
In-Reply-To: <3ec40c94-ad7f-4985-bb40-275ebc6427bd@kernel.dk>
On Fri, Jul 11, 2025 at 07:46:08AM -0600, Jens Axboe wrote:
> On 7/11/25 5:22 AM, Christoph Hellwig wrote:
> > Not only do IOVA mappings no need the separate dma_vec tracking, it
> > also won't free it and thus leak the allocations.
> >
> > Fixes: 10f50d4127e2 ("nvme-pci: fix dma unmapping when using PRPs and not using the IOVA mapping")
> ^^^^^^^^^^^^
>
> b8b7570a7ec872f2a27b775c4f8710ca8a357adf
Ah, sorry. That was the commit ID in my tree before I sent the original
patch out.
next prev parent reply other threads:[~2025-07-14 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 11:22 [PATCH] nvme-pci: don't allocate dma_vec for IOVA mappings Christoph Hellwig
2025-07-11 13:46 ` Jens Axboe
2025-07-14 11:42 ` Christoph Hellwig [this message]
2025-07-11 13:46 ` Jens Axboe
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=20250714114213.GA1998@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=klarasmodin@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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 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.