From: Ondrej Mosnacek <omosnace@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: netdev@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: [PATCH v2 0/2] cipso: make cipso_v4_skbuff_delattr() fully remove the CIPSO options
Date: Fri, 7 Jun 2024 18:07:51 +0200 [thread overview]
Message-ID: <20240607160753.1787105-1-omosnace@redhat.com> (raw)
This series aims to improve cipso_v4_skbuff_delattr() to fully
remove the CIPSO options instead of just clearing them with NOPs.
That is implemented in the second patch, while the first patch is
a bugfix for cipso_v4_delopt() that the second patch depends on.
Tested using selinux-testsuite a TMT/Beakerlib test from this PR:
https://src.fedoraproject.org/tests/selinux/pull-request/488
Changes in v2:
- drop the paranoid WARN_ON() usage
- reword the description of the second patch
v1: https://lore.kernel.org/linux-security-module/20240416152913.1527166-1-omosnace@redhat.com/
Ondrej Mosnacek (2):
cipso: fix total option length computation
cipso: make cipso_v4_skbuff_delattr() fully remove the CIPSO options
net/ipv4/cipso_ipv4.c | 75 +++++++++++++++++++++++++++++++------------
1 file changed, 54 insertions(+), 21 deletions(-)
--
2.45.1
next reply other threads:[~2024-06-07 16:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 16:07 Ondrej Mosnacek [this message]
2024-06-07 16:07 ` [PATCH v2 1/2] cipso: fix total option length computation Ondrej Mosnacek
2024-06-07 16:07 ` [PATCH v2 2/2] cipso: make cipso_v4_skbuff_delattr() fully remove the CIPSO options Ondrej Mosnacek
2024-06-07 18:50 ` [PATCH v2 0/2] " Casey Schaufler
2024-06-10 15:14 ` Ondrej Mosnacek
2024-06-10 16:53 ` Casey Schaufler
2024-06-11 9:42 ` Ondrej Mosnacek
2024-06-14 7:20 ` patchwork-bot+netdevbpf
2024-06-14 15:08 ` Paul Moore
2024-06-19 2:46 ` Paul Moore
2024-06-20 10:02 ` Ondrej Mosnacek
2024-06-20 14:39 ` Paul Moore
2024-07-26 12:44 ` Ondrej Mosnacek
2024-07-26 19:41 ` Paul Moore
2024-06-14 7:30 ` patchwork-bot+netdevbpf
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=20240607160753.1787105-1-omosnace@redhat.com \
--to=omosnace@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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