Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Or Har-Toov <ohartoov@nvidia.com>,
	linux-rdma@vger.kernel.org,
	Patrisious Haddad <phaddad@nvidia.com>
Subject: Re: [PATCH rdma-rc] RDMA/mlx5: Fix unsafe xarray access in implicit ODP handling
Date: Tue, 17 Jun 2025 14:40:42 -0300	[thread overview]
Message-ID: <20250617174042.GA1569186@nvidia.com> (raw)
In-Reply-To: <a85ddd16f45c8cb2bc0a188c2b0fcedfce975eb8.1750061791.git.leon@kernel.org>

On Mon, Jun 16, 2025 at 11:17:01AM +0300, Leon Romanovsky wrote:
> From: Or Har-Toov <ohartoov@nvidia.com>
> 
> __xa_store() and __xa_erase() were used without holding the proper lock,
> which led to a lockdep warning due to unsafe RCPU usage.
> This patch replaces them with xa_store() and xa_erase(), which perform
> the necessary locking internally.
> 
> =============================
> WARNING: suspicious RCPU usage
> 6.14.0-rc7_for_upstream_debug_2025_03_18_15_01 #1 Not tainted
> -----------------------------
> ./include/linux/xarray.h:1211 suspicious rcu_dereference_protected()
> usage!
> 
> other info that might help us debug this:
> 
> rcu_scheduler_active = 2, debug_locks = 1
> 3 locks held by kworker/u136:0/219:
>     at: process_one_work+0xbe4/0x15f0
>     process_one_work+0x75c/0x15f0
>     pagefault_mr+0x9a5/0x1390 [mlx5_ib]
> 
> stack backtrace:
> CPU: 14 UID: 0 PID: 219 Comm: kworker/u136:0 Not tainted
> 6.14.0-rc7_for_upstream_debug_2025_03_18_15_01 #1
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
> rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
> Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib]
> Call Trace:

Don't work wrap oops messages.. Ignore the checkpatch thing that tells
you to do that.

Applied to for-rc

Thanks,
Jason

      reply	other threads:[~2025-06-17 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  8:17 [PATCH rdma-rc] RDMA/mlx5: Fix unsafe xarray access in implicit ODP handling Leon Romanovsky
2025-06-17 17:40 ` 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=20250617174042.GA1569186@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=ohartoov@nvidia.com \
    --cc=phaddad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox