From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Cliff Liu <donghua.liu@windriver.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y] bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
Date: Wed, 2 Apr 2025 17:24:58 -0400 [thread overview]
Message-ID: <20250402124727-e5de7a5a0e0983ef@stable.kernel.org> (raw)
In-Reply-To: <20250402030457.617254-1-donghua.liu@windriver.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 169410eba271afc9f0fb476d996795aa26770c6d
WARNING: Author mismatch between patch and upstream commit:
Backport author: Cliff Liu<donghua.liu@windriver.com>
Commit author: Hou Tao<houtao1@huawei.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 483cb92334cd)
6.1.y | Present (different SHA1: d6d6fe4bb105)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 169410eba271a < -: ------------- bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
-: ------------- > 1: 39bb26e992067 bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Success | Success |
prev parent reply other threads:[~2025-04-02 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 3:04 [PATCH 5.10.y] bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers Cliff Liu
2025-04-02 21:24 ` 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=20250402124727-e5de7a5a0e0983ef@stable.kernel.org \
--to=sashal@kernel.org \
--cc=donghua.liu@windriver.com \
--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