From: patchwork-bot+netdevbpf@kernel.org
To: Jann Horn <jannh@google.com>
Cc: paul@paul-moore.com, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, jmorris@namei.org,
serge@hallyn.com, horms@kernel.org,
stephen.smalley.work@gmail.com, omosnacek@gmail.com,
casey@schaufler-ca.com, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, selinux@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] cipso: stop modifying live ip_options_rcu
Date: Wed, 11 Nov 2026 00:50:05 +0000 [thread overview]
Message-ID: <179435820518.142717.5535232865040780378.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106-cipso-rcuopts-v1-1-31ae931d7a0f@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 06 Nov 2026 22:40:31 +0100 you wrote:
> cipso_v4_delopt() operates on the ip_options_rcu of a socket or a request
> socket, and tries to remove CIPSO options from the middle by moving all
> subsequent options.
> That's not allowed - ip_options_rcu can be read locklessly and must always
> be consistent. For example, ip_options_undo() reads trusted offsets and
> length values from the options buffer.
> Fix it by doing the modification in a copy.
>
> [...]
Here is the summary with links:
- [net] cipso: stop modifying live ip_options_rcu
https://git.kernel.org/netdev/net/c/1f2c5183fc09
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-11 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 21:40 [PATCH net] cipso: stop modifying live ip_options_rcu Jann Horn
2026-11-06 23:06 ` Eric Dumazet
2026-11-09 20:14 ` Paul Moore
2026-11-10 16:41 ` Casey Schaufler
2026-11-09 20:13 ` Paul Moore
2026-11-10 16:13 ` Casey Schaufler
2026-11-10 16:10 ` Casey Schaufler
2026-11-11 0:50 ` patchwork-bot+netdevbpf [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=179435820518.142717.5535232865040780378.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jannh@google.com \
--cc=jmorris@namei.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omosnacek@gmail.com \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=stephen.smalley.work@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 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.