From: "Mickaël Salaün" <mic@digikod.net>
To: Mikhail Ivanov <ivanov.mikhail1@huawei-partners.com>
Cc: gnoack@google.com, willemdebruijn.kernel@gmail.com,
matthieu@buffet.re, linux-security-module@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
yusongping@huawei.com, artem.kuzin@huawei.com,
konstantin.meskhidze@huawei.com
Subject: Re: [RFC PATCH v3 0/3] Fix non-TCP sockets restriction
Date: Fri, 21 Feb 2025 17:09:35 +0100 [thread overview]
Message-ID: <20250221.yie2Naiquea0@digikod.net> (raw)
In-Reply-To: <20250205093651.1424339-1-ivanov.mikhail1@huawei-partners.com>
Thanks Mikhail, it's been in my tree for more than 10 days, I'll include
it in a fix PR next week.
On Wed, Feb 05, 2025 at 05:36:48PM +0800, Mikhail Ivanov wrote:
> Hello!
>
> This patch fixes incorrect restriction of non-TCP bind/connect actions.
> There is two commits that extend TCP tests with MPTCP test suits and
> IPPROTO_TCP test suits.
>
> Closes: https://github.com/landlock-lsm/linux/issues/40
>
> General changes after v2
> ========================
> * Rebases on current linux-mic/next
> * Extracts non-TCP restriction fix into separate patchset
>
> Previous versions
> =================
> v2: https://lore.kernel.org/all/20241017110454.265818-1-ivanov.mikhail1@huawei-partners.com/
> v1: https://lore.kernel.org/all/20241003143932.2431249-1-ivanov.mikhail1@huawei-partners.com/
>
> Mikhail Ivanov (3):
> landlock: Fix non-TCP sockets restriction
> selftests/landlock: Test TCP accesses with protocol=IPPROTO_TCP
> selftests/landlock: Test that MPTCP actions are not restricted
>
> security/landlock/net.c | 3 +-
> tools/testing/selftests/landlock/common.h | 1 +
> tools/testing/selftests/landlock/config | 2 +
> tools/testing/selftests/landlock/net_test.c | 124 +++++++++++++++++---
> 4 files changed, 114 insertions(+), 16 deletions(-)
>
>
> base-commit: 24a8e44deae4b549b0fe5fbb271fe8d169f0933f
> --
> 2.34.1
>
>
prev parent reply other threads:[~2025-02-21 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 9:36 [RFC PATCH v3 0/3] Fix non-TCP sockets restriction Mikhail Ivanov
2025-02-05 9:36 ` [RFC PATCH v3 1/3] landlock: " Mikhail Ivanov
2025-02-05 9:36 ` [RFC PATCH v3 2/3] selftests/landlock: Test TCP accesses with protocol=IPPROTO_TCP Mikhail Ivanov
2025-02-05 9:36 ` [RFC PATCH v3 3/3] selftests/landlock: Test that MPTCP actions are not restricted Mikhail Ivanov
2025-02-21 16:09 ` Mickaël Salaün [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=20250221.yie2Naiquea0@digikod.net \
--to=mic@digikod.net \
--cc=artem.kuzin@huawei.com \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-security-module@vger.kernel.org \
--cc=matthieu@buffet.re \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yusongping@huawei.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.