From: David Laight <david.laight.linux@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/2] nvme-pci: Use size_t for length fields to handle larger sizes
Date: Sat, 15 Nov 2025 17:33:41 +0000 [thread overview]
Message-ID: <20251115173341.4a59c97f@pumpkin> (raw)
In-Reply-To: <20251115-nvme-phys-types-v1-1-c0f2e5e9163d@kernel.org>
On Sat, 15 Nov 2025 18:22:45 +0200
Leon Romanovsky <leon@kernel.org> wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> This patch changes the length variables from unsigned int to size_t.
> Using size_t ensures that we can handle larger sizes, as size_t is
> always equal to or larger than the previously used u32 type.
Where are requests larger than 4GB going to come from?
> Originally, u32 was used because blk-mq-dma code evolved from
> scatter-gather implementation, which uses unsigned int to describe length.
> This change will also allow us to reuse the existing struct phys_vec in places
> that don't need scatter-gather.
>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
> block/blk-mq-dma.c | 14 +++++++++-----
> drivers/nvme/host/pci.c | 4 ++--
> 2 files changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/block/blk-mq-dma.c b/block/blk-mq-dma.c
> index e9108ccaf4b0..cc3e2548cc30 100644
> --- a/block/blk-mq-dma.c
> +++ b/block/blk-mq-dma.c
> @@ -8,7 +8,7 @@
>
> struct phys_vec {
> phys_addr_t paddr;
> - u32 len;
> + size_t len;
> };
>
> static bool __blk_map_iter_next(struct blk_map_iter *iter)
> @@ -112,8 +112,8 @@ static bool blk_rq_dma_map_iova(struct request *req, struct device *dma_dev,
> struct phys_vec *vec)
> {
> enum dma_data_direction dir = rq_dma_dir(req);
> - unsigned int mapped = 0;
> unsigned int attrs = 0;
> + size_t mapped = 0;
> int error;
>
> iter->addr = state->addr;
> @@ -296,8 +296,10 @@ int __blk_rq_map_sg(struct request *rq, struct scatterlist *sglist,
> blk_rq_map_iter_init(rq, &iter);
> while (blk_map_iter_next(rq, &iter, &vec)) {
> *last_sg = blk_next_sg(last_sg, sglist);
> - sg_set_page(*last_sg, phys_to_page(vec.paddr), vec.len,
> - offset_in_page(vec.paddr));
> +
> + WARN_ON_ONCE(overflows_type(vec.len, unsigned int));
I'm not at all sure you need that test.
blk_map_iter_next() has to guarantee that vec.len is valid.
(probably even less than a page size?)
Perhaps this code should be using a different type for the addr:len pair?
> + sg_set_page(*last_sg, phys_to_page(vec.paddr),
> + (unsigned int)vec.len, offset_in_page(vec.paddr));
You definitely don't need the explicit cast.
David
> nsegs++;
> }
>
> @@ -416,7 +418,9 @@ int blk_rq_map_integrity_sg(struct request *rq, struct scatterlist *sglist)
>
> while (blk_map_iter_next(rq, &iter, &vec)) {
> sg = blk_next_sg(&sg, sglist);
> - sg_set_page(sg, phys_to_page(vec.paddr), vec.len,
> +
> + WARN_ON_ONCE(overflows_type(vec.len, unsigned int));
> + sg_set_page(sg, phys_to_page(vec.paddr), (unsigned int)vec.len,
> offset_in_page(vec.paddr));
> segments++;
> }
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 9085bed107fd..de512efa742d 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -290,14 +290,14 @@ struct nvme_iod {
> u8 flags;
> u8 nr_descriptors;
>
> - unsigned int total_len;
> + size_t total_len;
> struct dma_iova_state dma_state;
> void *descriptors[NVME_MAX_NR_DESCRIPTORS];
> struct nvme_dma_vec *dma_vecs;
> unsigned int nr_dma_vecs;
>
> dma_addr_t meta_dma;
> - unsigned int meta_total_len;
> + size_t meta_total_len;
> struct dma_iova_state meta_dma_state;
> struct nvme_sgl_desc *meta_descriptor;
> };
>
next prev parent reply other threads:[~2025-11-15 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 16:22 [PATCH 0/2] block: Generalize physical entry definition Leon Romanovsky
2025-11-15 16:22 ` [PATCH 1/2] nvme-pci: Use size_t for length fields to handle larger sizes Leon Romanovsky
2025-11-15 17:33 ` David Laight [this message]
2025-11-15 18:05 ` Leon Romanovsky
2025-11-15 22:28 ` David Laight
2025-11-16 7:14 ` Leon Romanovsky
2025-11-15 22:25 ` Chaitanya Kulkarni
2025-11-15 16:22 ` [PATCH 2/2] types: move phys_vec definition to common header Leon Romanovsky
2025-11-15 22:25 ` Chaitanya Kulkarni
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=20251115173341.4a59c97f@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=leon@kernel.org \
--cc=linux-block@vger.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