From: Leon Romanovsky <leon@kernel.org>
To: lirongqing <lirongqing@baidu.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Michael Guralnik <michaelgur@nvidia.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/mlx5: Wait for in-flight page faults on implicit MR null_mkey dereg
Date: Mon, 28 Sep 2026 21:59:03 +0300 [thread overview]
Message-ID: <20260928185903.GA563127@unreal> (raw)
In-Reply-To: <20260920090613.2186-1-lirongqing@baidu.com>
On Sun, Sep 20, 2026 at 05:06:13PM +0800, lirongqing wrote:
> From: Li RongQing <lirongqing@baidu.com>
>
> An implicit ODP MR (imr) publishes two mkeys into dev->odp_mkeys: the
> main imr->mmkey and imr->null_mmkey (MLX5_MKEY_NULL). Both are stored via
> mlx5r_store_odp_mkey(), which initialises their usecount to 1, and
> find_odp_mkey() takes a reference on whichever mkey it finds for the
> duration of a page fault.
>
> __mlx5_ib_dereg_mr() erases and waits on the *main* mmkey usecount only.
> For the null_mmkey, mlx5_ib_free_odp_mr() merely xa_erase()s it from
> odp_mkeys and calls mlx5_core_destroy_mkey() -- it never waits for an
> in-flight memory-scheme page fault (MLX5_MKEY_NULL) that holds a
> reference on null_mmkey. After xa_erase(), find_odp_mkey() stops
> returning the null_mmkey, but a fault already past the lookup still
> holds a reference and dereferences the imr (via container_of and
> pagefault_mr) after __mlx5_ib_dereg_mr() proceeds to kfree(mr).
I'm not sure that your scenario is real. Null mkey is special case to
allow split of large address space faults to smaller chunks.
Thanks
>
> Mirror the main-mmkey handling: after xa_erase() of null_mmkey, call
> mlx5r_deref_wait_odp_mkey() to drop the reference taken at store time
> and wait for any in-flight fault to finish before destroying the mkey
> and freeing the imr.
>
> Fixes: 6f2487bfafce ("RDMA/mlx5: Add implicit MR handling to ODP memory scheme")
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> drivers/infiniband/hw/mlx5/odp.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/infiniband/hw/mlx5/odp.c b/drivers/infiniband/hw/mlx5/odp.c
> index b861861..f27ca77 100644
> --- a/drivers/infiniband/hw/mlx5/odp.c
> +++ b/drivers/infiniband/hw/mlx5/odp.c
> @@ -683,6 +683,8 @@ void mlx5_ib_free_odp_mr(struct mlx5_ib_mr *mr)
> xa_erase(&mr_to_mdev(mr)->odp_mkeys,
> mlx5_base_mkey(mr->null_mmkey.key));
>
> + mlx5r_deref_wait_odp_mkey(&mr->null_mmkey);
> +
> mlx5_core_destroy_mkey(mr_to_mdev(mr)->mdev,
> mr->null_mmkey.key);
> }
> --
> 2.9.4
>
next prev parent reply other threads:[~2026-09-28 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 9:06 [PATCH] RDMA/mlx5: Wait for in-flight page faults on implicit MR null_mkey dereg lirongqing
2026-09-20 9:21 ` sashiko-bot
2026-09-28 18:59 ` Leon Romanovsky [this message]
2026-09-28 22:44 ` Michael Gur
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=20260928185903.GA563127@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=michaelgur@nvidia.com \
/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.