From: "Maurizio Lombardi" <mlombard@arkamax.eu>
To: "Joel Granados" <joel.granados@kernel.org>,
"Keith Busch" <kbusch@kernel.org>, "Jens Axboe" <axboe@kernel.dk>,
"Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>
Cc: "Daniel Gomez" <da.gomez@kernel.org>,
<linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvme: unmap the data buffer when metadata mapping fails
Date: Fri, 12 Jun 2026 11:45:26 +0200 [thread overview]
Message-ID: <DJ6Z3EVG32PV.1CXC6PRBH1CIY@arkamax.eu> (raw)
In-Reply-To: <20260612-jag-fixes-v1-1-24423dc8afdb@kernel.org>
On Fri Jun 12, 2026 at 11:40 AM CEST, Joel Granados wrote:
> Commit d0d1d522316e ("blk-map: provide the bdev to bio if one exists")
> dropped the "bio = req->bio" assignment in nvme_map_user_request(), but
> left the local bio variable initialized to NULL and still used it in the
> out_unmap error path. The "if (bio)" test is therefore always false, so
> a failure of blk_rq_integrity_map_user() no longer unmaps the already
> mapped data buffer. The callers only call blk_mq_free_request(), which
> does not unmap user pages, leaking the bio and its pinned user pages.
>
> Use req->bio directly to unmap the data buffer on the error path, and
> drop the now unused local variable.
>
> Fixes: d0d1d522316e ("blk-map: provide the bdev to bio if one exists")
>
> Signed-off-by: Joel Granados <joel.granados@kernel.org>
> ---
> Did we forget to unmap?
> ---
Isn't this already fixed in mainline tree?
2279cd9c61a330e5 ("nvme: fix bio leak on mapping failure")
Maurizio
> drivers/nvme/host/ioctl.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/nvme/host/ioctl.c b/drivers/nvme/host/ioctl.c
> index 9597a87cf05dc32a7eb0373485f575502c32a105..9ae3c0aadfb8f35790c8e57619d1af69ca41af0c 100644
> --- a/drivers/nvme/host/ioctl.c
> +++ b/drivers/nvme/host/ioctl.c
> @@ -122,7 +122,6 @@ static int nvme_map_user_request(struct request *req, u64 ubuffer,
> bool supports_metadata = bdev && blk_get_integrity(bdev->bd_disk);
> struct nvme_ctrl *ctrl = nvme_req(req)->ctrl;
> bool has_metadata = meta_buffer && meta_len;
> - struct bio *bio = NULL;
> int ret;
>
> if (!nvme_ctrl_sgl_supported(ctrl))
> @@ -154,8 +153,8 @@ static int nvme_map_user_request(struct request *req, u64 ubuffer,
> return ret;
>
> out_unmap:
> - if (bio)
> - blk_rq_unmap_user(bio);
> + if (req->bio)
> + blk_rq_unmap_user(req->bio);
> return ret;
> }
>
>
> ---
> base-commit: adeac771f4901bb66267eaddb9fcc538925f92a4
> change-id: 20260612-jag-fixes-6b459ea16d53
>
> Best regards,
next prev parent reply other threads:[~2026-06-12 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 9:40 Joel Granados
2026-06-12 9:45 ` Maurizio Lombardi [this message]
2026-06-17 14:09 ` Joel Granados
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=DJ6Z3EVG32PV.1CXC6PRBH1CIY@arkamax.eu \
--to=mlombard@arkamax.eu \
--cc=axboe@kernel.dk \
--cc=da.gomez@kernel.org \
--cc=hch@lst.de \
--cc=joel.granados@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-kernel@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 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®