From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
Vladislav Nikolaev <vlad102nikolaev@gmail.com>,
Zhu Yanjun <zyjzyj2000@gmail.com>,
Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Haggai Eran <haggaie@mellanox.com>,
Kamal Heib <kamalh@mellanox.com>, Amir Vadai <amirv@mellanox.com>,
Moni Shoua <monis@mellanox.com>,
Yonatan Cohen <yonatanc@mellanox.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhu Yanjun <yanjunz@nvidia.com>,
lvc-project@linuxtesting.org,
syzbot+cfcc1a3c85be15a40cba@syzkaller.appspotmail.com,
Zhu Yanjun <yanjun.zhu@linux.dev>
Subject: Re: [PATCH v2 5.10/5.15] RDMA/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task"
Date: Fri, 5 Jun 2026 15:37:28 -0400 [thread overview]
Message-ID: <20260605-stable-reply-0021@kernel.org> (raw)
In-Reply-To: <20260603121902.274-1-vlad102nikolaev@gmail.com>
> [PATCH v2 5.10/5.15] RDMA/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task"
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,
Sasha
prev parent reply other threads:[~2026-06-05 19:37 UTC|newest]
Thread overview: 4+ 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 [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=20260605-stable-reply-0021@kernel.org \
--to=sashal@kernel.org \
--cc=amirv@mellanox.com \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=haggaie@mellanox.com \
--cc=jgg@ziepe.ca \
--cc=kamalh@mellanox.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=monis@mellanox.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+cfcc1a3c85be15a40cba@syzkaller.appspotmail.com \
--cc=vlad102nikolaev@gmail.com \
--cc=yanjun.zhu@linux.dev \
--cc=yanjunz@nvidia.com \
--cc=yonatanc@mellanox.com \
--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