From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Srish Srinivasan <srishwap4@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v5.10] bpf: fix recursive lock when verdict program return SK_PASS
Date: Sun, 29 Dec 2024 11:09:58 -0500 [thread overview]
Message-ID: <20241229105403-9a5e93ba8876b6bd@stable.kernel.org> (raw)
In-Reply-To: <20241228191415.41473-1-srishwap4@gmail.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 8ca2a1eeadf09862190b2810697702d803ceef2d
WARNING: Author mismatch between patch and upstream commit:
Backport author: Srish Srinivasan<srishwap4@gmail.com>
Commit author: Jiayuan Chen<mrpre@163.com>
Status in newer kernel trees:
6.12.y | Present (different SHA1: f84c5ef6ca23)
6.6.y | Present (different SHA1: da2bc8a0c8f3)
6.1.y | Present (different SHA1: 386efa339e08)
5.15.y | Present (different SHA1: 6694f7acd625)
5.10.y | Not found
Note: The patch differs from the upstream commit:
---
1: 8ca2a1eeadf0 ! 1: 3487de836032 bpf: fix recursive lock when verdict program return SK_PASS
@@ Metadata
## Commit message ##
bpf: fix recursive lock when verdict program return SK_PASS
+ commit 8ca2a1eeadf09862190b2810697702d803ceef2d upstream.
+
When the stream_verdict program returns SK_PASS, it places the received skb
into its own receive queue, but a recursive lock eventually occurs, leading
to an operating system deadlock. This issue has been present since v6.9.
@@ Commit message
Acked-by: Martin KaFai Lau <martin.lau@kernel.org>
Link: https://patch.msgid.link/20241118030910.36230-2-mrpre@163.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+ Signed-off-by: Sasha Levin <sashal@kernel.org>
+ [srish: Apply to stable branch linux-5.10.y]
+ Signed-off-by: Srish Srinivasan <srishwap4@gmail.com>
## net/core/skmsg.c ##
@@ net/core/skmsg.c: static void sk_psock_strp_data_ready(struct sock *sk)
if (tls_sw_has_ctx_rx(sk)) {
- psock->saved_data_ready(sk);
+ psock->parser.saved_data_ready(sk);
} else {
- write_lock_bh(&sk->sk_callback_lock);
+ read_lock_bh(&sk->sk_callback_lock);
- strp_data_ready(&psock->strp);
+ strp_data_ready(&psock->parser.strp);
- write_unlock_bh(&sk->sk_callback_lock);
+ read_unlock_bh(&sk->sk_callback_lock);
}
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Success | Success |
prev parent reply other threads:[~2024-12-29 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 19:14 [PATCH v5.10] bpf: fix recursive lock when verdict program return SK_PASS Srish Srinivasan
2024-12-29 16:09 ` 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=20241229105403-9a5e93ba8876b6bd@stable.kernel.org \
--to=sashal@kernel.org \
--cc=srishwap4@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.