From: Leon Romanovsky <leon@kernel.org>
To: jgg@ziepe.ca, Abhijit Gangurde <abhijit.gangurde@amd.com>
Cc: allen.hubbe@amd.com, nikhil.agarwal@amd.com,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] RDMA/ionic: Fix XArray initialization to use XArray flags
Date: Tue, 29 Sep 2026 14:45:43 -0400 [thread overview]
Message-ID: <179070754326.3974961.446550706671419287.b4-ty@kernel.org> (raw)
In-Reply-To: <20260925093638.3032149-1-abhijit.gangurde@amd.com>
On Fri, 25 Sep 2026 15:06:37 +0530, Abhijit Gangurde wrote:
> xa_init_flags() takes XArray flags (XA_FLAGS_*), not gfp flags, even
> though the parameter is typed gfp_t. Passing GFP_ATOMIC leaves both
> lock-type bits clear, so xa_lock_type() resolves to XA_LOCK_NORMAL for
> qp_tbl and cq_tbl.
>
> Both tables are used with the IRQ-safe accessors: xa_store_irq() with
> GFP_KERNEL from process context, and xa_lock_irqsave() from the event
> queue path. When a store needs to grow the tree, __xas_nomem() drops
> the lock using the recorded lock type before allocating:
>
> [...]
Applied, thanks!
[1/2] RDMA/ionic: Fix XArray initialization to use XArray flags
https://git.kernel.org/rdma/rdma/c/2eca9c14e66a1f
[2/2] RDMA/ionic: Fix double removal of CMB mmap entries in create QP error path
https://git.kernel.org/rdma/rdma/c/485effd117d031
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-09-29 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 9:36 [PATCH 1/2] RDMA/ionic: Fix XArray initialization to use XArray flags Abhijit Gangurde
2026-09-25 9:36 ` [PATCH 2/2] RDMA/ionic: Fix double removal of CMB mmap entries in create QP error path Abhijit Gangurde
2026-09-25 9:46 ` sashiko-bot
2026-09-25 9:41 ` [PATCH 1/2] RDMA/ionic: Fix XArray initialization to use XArray flags sashiko-bot
2026-09-29 18:45 ` Leon Romanovsky [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=179070754326.3974961.446550706671419287.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=abhijit.gangurde@amd.com \
--cc=allen.hubbe@amd.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nikhil.agarwal@amd.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