From: Sabrina Dubroca <sd@queasysnail.net>
To: netdev@vger.kernel.org
Cc: Sabrina Dubroca <sd@queasysnail.net>,
Steffen Klassert <steffen.klassert@secunet.com>,
Antony Antony <antony.antony@secunet.com>,
Tobias Brunner <tobias@strongswan.org>,
Florian Westphal <fw@strlen.de>
Subject: [PATCH ipsec 0/2] xfrm: fixes for xfrm_state_find under preemption
Date: Fri, 23 May 2025 17:11:16 +0200 [thread overview]
Message-ID: <cover.1748001837.git.sd@queasysnail.net> (raw)
While looking at the pcpu_id changes, I found two issues that can
happen if we get preempted and the cpu_id changes. The second patch
takes care of both problems. The first patch also makes sure we don't
use state_ptrs uninitialized, which could currently happen. syzbot
seems to have hit this issue [1].
[1] https://syzkaller.appspot.com/bug?extid=7ed9d47e15e88581dc5b
Sabrina Dubroca (2):
xfrm: state: initialize state_ptrs earlier in xfrm_state_find
xfrm: state: use a consistent pcpu_id for xfrm_state_find
net/xfrm/xfrm_state.c | 23 ++++++++---------------
1 file changed, 8 insertions(+), 15 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-23 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 15:11 Sabrina Dubroca [this message]
2025-05-23 15:11 ` [PATCH ipsec 1/2] xfrm: state: initialize state_ptrs earlier in xfrm_state_find Sabrina Dubroca
2025-05-23 18:05 ` Florian Westphal
2025-05-23 15:11 ` [PATCH ipsec 2/2] xfrm: state: use a consistent pcpu_id " Sabrina Dubroca
2025-05-23 18:12 ` Florian Westphal
2025-05-26 6:28 ` Steffen Klassert
2025-05-26 13:57 ` Florian Westphal
2025-05-26 12:17 ` Steffen Klassert
2025-06-10 7:55 ` [PATCH ipsec 0/2] xfrm: fixes for xfrm_state_find under preemption Steffen Klassert
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=cover.1748001837.git.sd@queasysnail.net \
--to=sd@queasysnail.net \
--cc=antony.antony@secunet.com \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=tobias@strongswan.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.