From: patchwork-bot+netdevbpf@kernel.org
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: paul@paul-moore.com, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 0/2] cipso: make cipso_v4_skbuff_delattr() fully remove the CIPSO options
Date: Fri, 14 Jun 2024 07:20:28 +0000 [thread overview]
Message-ID: <171834962895.31068.8051988032320283876.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240607160753.1787105-1-omosnace@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 7 Jun 2024 18:07:51 +0200 you wrote:
> 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
>
> [...]
Here is the summary with links:
- [v2,1/2] cipso: fix total option length computation
https://git.kernel.org/netdev/net/c/9f3616991233
- [v2,2/2] cipso: make cipso_v4_skbuff_delattr() fully remove the CIPSO options
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-06-14 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 16:07 [PATCH v2 0/2] cipso: make cipso_v4_skbuff_delattr() fully remove the CIPSO options Ondrej Mosnacek
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 [this message]
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=171834962895.31068.8051988032320283876.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omosnace@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 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.