From: Vladislav Nikolaev <vlad102nikolaev@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Vladislav Nikolaev <vlad102nikolaev@gmail.com>,
stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Zhu Yanjun <zyjzyj2000@gmail.com>,
Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Haggai Eran <haggaie@mellanox.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Fedor Pchelkin <pchelkin@ispras.ru>,
lvc-project@linuxtesting.org
Subject:
Date: Tue, 9 Jun 2026 17:54:31 +0300 [thread overview]
Message-ID: <20260609145437.1837-1-vlad102nikolaev@gmail.com> (raw)
In-Reply-To: <20260605-stable-reply-0021@kernel.org>
Subject: Re: [PATCH v2 5.10/5.15] RDMA/rxe: Fix the error "trying to register
non-static key in rxe_cleanup_task"
In-Reply-To: <20260605-stable-reply-0021@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
On Fri, Jun 05, 2026 at 03:37:28PM -0400, Sasha Levin wrote:
> I'm dropping this for now; it isn't right for either branch as submitted:
>
> - 5.15.y: the bug doesn't exist there -- the task locks are already
> spin_lock_init()'d on the QP-create error path.
> - 5.10.y: mis-targeted -- it patches rxe_qp_do_cleanup(), but the 5.10
> error-unwind path doesn't call rxe_cleanup_task() there.
Thanks for checking this.
I rechecked the 5.10.y and 5.15.y code paths, and I agree with your
assessment. This is not a correct backport for these branches.
Sorry for the noise.
next prev parent reply other threads:[~2026-06-09 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 12:18 [PATCH v2 5.10/5.15] RDMA/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task" Vladislav Nikolaev
2026-06-03 15:03 ` [lvc-project] " Fedor Pchelkin
2026-06-05 17:37 ` Vladislav Nikolaev
2026-06-05 19:37 ` Sasha Levin
2026-06-09 14:54 ` Vladislav Nikolaev [this message]
2026-06-09 14:56 ` Vladislav Nikolaev
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=20260609145437.1837-1-vlad102nikolaev@gmail.com \
--to=vlad102nikolaev@gmail.com \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=haggaie@mellanox.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zyjzyj2000@gmail.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
all inboxes | Powered by JetHome®