Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>, linux-rdma@vger.kernel.org
Cc: patches@lists.linux.dev, Shiraz Saleem <shiraz.saleem@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix typing issues in the umem code
Date: Wed, 3 Jun 2026 09:41:06 -0300	[thread overview]
Message-ID: <20260603124106.GA1429219@nvidia.com> (raw)
In-Reply-To: <0-v1-88303e9e509f+f7-ib_umem_types_jgg@nvidia.com>

On Mon, Jun 01, 2026 at 01:52:30PM -0300, Jason Gunthorpe wrote:
> The types are tricky here as we have a mixture of u64, dma_addr_t and
> unsigned long used purposefully for different things:
>  - The on-the-wire IOVA address of the MR is u64
>  - The dma address is dma_addr_t which can be u32 or u64
>  - unsigned long is used for pgsize, mostly because a bunch of bit math
>    helper functions are used and they are obnoxious to use u64
> 
> Fix various silent truncations, issues on 32 bit compiles and
> understandability.
> 
> Jason Gunthorpe (3):
>   RDMA/umem: Fix truncation for block sizes >= 4G
>   RDMA/umem: Be careful about boundary conditions in
>     ib_umem_find_best_pgsz()
>   RDMA/umem: Make ib_umem_is_contiguous() safe on 32 bit

I picked up t he first patch to -rc

Jason

      parent reply	other threads:[~2026-06-03 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 16:52 [PATCH 0/3] Fix typing issues in the umem code Jason Gunthorpe
2026-06-01 16:52 ` [PATCH 1/3] RDMA/umem: Fix truncation for block sizes >= 4G Jason Gunthorpe
2026-06-01 16:52 ` [PATCH 2/3] RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() Jason Gunthorpe
2026-06-01 16:52 ` [PATCH 3/3] RDMA/umem: Make ib_umem_is_contiguous() safe on 32 bit Jason Gunthorpe
2026-06-03 12:41 ` Jason Gunthorpe [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=20260603124106.GA1429219@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=shiraz.saleem@intel.com \
    --cc=stable@vger.kernel.org \
    /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