Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	leon@kernel.org, jgg@ziepe.ca, kaishen@linux.alibaba.com,
	Cheng Xu <chengyou@linux.alibaba.com>
Subject: Re: [PATCH 6.6.y] RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables
Date: Tue, 17 Nov 2026 19:19:53 -0500	[thread overview]
Message-ID: <2026-11-17-1-daily-reply-0002@kernel.org> (raw)
In-Reply-To: <20261117022839.23186-1-chengyou@linux.alibaba.com>

> Use IRQ-safe XArray helpers for all QP and CQ create-path updates,
> including the GSI QP store and error paths.

Queued for 6.12 and 6.6, thanks.

6.1 has the same bug and is not covered. If you want it there, please send a
6.1.y backport.

-- 
Thanks,
Sasha

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	leon@kernel.org, jgg@ziepe.ca, kaishen@linux.alibaba.com,
	Cheng Xu <chengyou@linux.alibaba.com>
Subject: Re: [PATCH 6.6.y] RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables
Date: Tue, 17 Nov 2026 19:22:48 -0500	[thread overview]
Message-ID: <2026-11-17-1-daily-reply-0002@kernel.org> (raw)
Message-ID: <20261118002248.wu4HjsFdDot26oHEK0Mwbq8yEcqH9lsR8E2s7HSq8Hc@z> (raw)
In-Reply-To: <20261117022839.23186-1-chengyou@linux.alibaba.com>

> Use IRQ-safe XArray helpers for all QP and CQ create-path updates,
> including the GSI QP store and error paths.

Queued for 6.12 and 6.6, thanks.

6.1 has the same bug and is not covered. If you want it there, please send a
6.1.y backport.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-11-18  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  2:28 [PATCH 6.6.y] RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables Cheng Xu
2026-11-18  0:19 ` Sasha Levin [this message]
2026-11-18  0:22   ` Sasha Levin

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=2026-11-17-1-daily-reply-0002@kernel.org \
    --to=sashal@kernel.org \
    --cc=chengyou@linux.alibaba.com \
    --cc=jgg@ziepe.ca \
    --cc=kaishen@linux.alibaba.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --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