From: Joas Antonio dos Santos <joasantonio108@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Paul Moore <paul@paul-moore.com>,
sashiko-reviews@lists.linux.dev,
linux-security-module@vger.kernel.org,
network dev <netdev@vger.kernel.org>
Subject: Re: [PATCH net v2] calipso: update payload_len when removing the CALIPSO option
Date: Thu, 15 Oct 2026 20:14:21 -0300 [thread overview]
Message-ID: <179210606199.96599.8994346249690707193@gmail.com> (raw)
In-Reply-To: <852c9fb6-6217-440a-968c-b5ab3e22dbc8@redhat.com>
On Thu, 15 Oct 2026, Paolo Abeni wrote:
> The above looks like a pre-existing issue, the patch itself looks
> correct, right?
Hi Paolo, Paul,
Yes, the issue is pre-existing; the delattr patch doesn't change it.
The skb_pull()/memmove()/skb_reset_network_header() sequence quoted
by Sashiko predates this patch, which only adjusts payload_len after
it.
I tested Paul's idea on top of both CALIPSO patches (QEMU, veth +
br0 with bridge-nf-call-ip6tables=1, SELinux + NetLabel CALIPSO
DOI 16):
- without it, a bridged CALIPSO packet towards an unlabeled
destination reaches the peer with a corrupted Ethernet header
(garbage dst MAC, ethertype 0x0000) and is dropped; an unlabeled
packet towards a CALIPSO-mapped destination never reaches the peer.
- with the nf_bridge_info_exists() check in selinux_ip_forward()
(plus a stub returning false for CONFIG_BRIDGE_NETFILTER=n),
5/5 packets are delivered unmodified in both cases.
- the routed path is unchanged: delattr 5/5, setattr still adds the
option 5/5. W=1 is clean with BRIDGE_NETFILTER=y and =n.
Paul, if you like I can send it as a separate selinux patch with your
Suggested-by.
Thanks,
Joas
next prev parent reply other threads:[~2026-10-15 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 15:28 [PATCH net v2] calipso: update payload_len when removing the CALIPSO option Joas Antonio dos Santos
[not found] ` <sashiko-outbox-165773@kernel.org>
[not found] ` <CAHC9VhS+bdL_YnLQtd0sPmKKfy9BvS-LWV_6EhAuu4qfUFe_mw@mail.gmail.com>
2026-10-15 10:47 ` Paolo Abeni
2026-10-15 23:14 ` Joas Antonio dos Santos [this message]
2026-10-16 2:07 ` Paul Moore
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=179210606199.96599.8994346249690707193@gmail.com \
--to=joasantonio108@gmail.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=sashiko-reviews@lists.linux.dev \
/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