Linux Security Modules development
 help / color / mirror / Atom feed
From: Joas Antonio dos Santos <joasantonio108@gmail.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Eric Dumazet <edumazet@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
	Alice Mikityanska <alice.kernel@fastmail.im>
Subject: Re: [PATCH net] calipso: update payload_len when removing the CALIPSO option
Date: Fri, 16 Oct 2026 11:26:14 -0300	[thread overview]
Message-ID: <179216077404.22091.15636720633867774901@gmail.com> (raw)
In-Reply-To: <CAHC9VhT5w3K1MvmP=1Mxf6KKWZD5BbK14bVHJGYFN93080j5jg@mail.gmail.com>

On Wed, Oct 14, 2026 at 9:39 AM Paul Moore wrote:
> while basic CALIPSO labeling is tested via an automated test job, this
> particular code path is not part of the automated testing.
> Improvements to the tests are always welcome.

Hi Paul,

I opened a PR adding a forwarding test to tests/inet_socket:

  https://github.com/SELinuxProject/selinux-testsuite/pull/106

It builds a client -- router -- server setup with network namespaces
and checks both directions: the router removing the CALIPSO option and
the router adding one.  On Fedora 44 (6.19.10, without the fix) only
the removal subtest fails, with the forwarded packet dropped as
truncated; with the fix all inet_socket and sctp tests pass, both as
unconfined_t and sysadm_t.

Until the fix reaches the kernel used by the CI, the removal subtest
will fail there; I'm happy to gate it on a kernel version if you
prefer.

Thanks,
Joas

  reply	other threads:[~2026-10-16 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 15:25 [PATCH net] calipso: update payload_len when removing the CALIPSO option Joas Antonio dos Santos
2026-10-07 20:45 ` Eric Dumazet
2026-10-14 13:39   ` Paul Moore
2026-10-16 14:26     ` Joas Antonio dos Santos [this message]
2026-10-08 15:26 ` sashiko-bot

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=179216077404.22091.15636720633867774901@gmail.com \
    --to=joasantonio108@gmail.com \
    --cc=alice.kernel@fastmail.im \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paul@paul-moore.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox