public inbox for linux-security-module@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it, linux-security-module@vger.kernel.org,
	"Mickaël Salaün" <mic@digikod.net>,
	"Günther Noack" <gnoack@google.com>
Subject: Re: [LTP] [PATCH 0/4] Landlock tests for ABI v6
Date: Thu, 27 Mar 2025 14:18:38 +0100	[thread overview]
Message-ID: <20250327131838.GB77751@pevik> (raw)
In-Reply-To: <20250327-landlock_unix_socket-v1-0-584653f66d9c@suse.com>

Hi all,

FYI new batch of Andrea's work on landlock test coverage in LTP.
Feel free to have a look.

https://patchwork.ozlabs.org/project/ltp/list/?series=450223&archive=both
https://lore.kernel.org/ltp/20250327-landlock_unix_socket-v1-0-584653f66d9c@suse.com/T/#t

Kind regards,
Petr

> Landlock released a new feature for IPC scoping in the new ABI.
> This includes the following new rules which will be tested in
> this patch-set:

> - LANDLOCK_SCOPE_ABSTRACT_UNIX_SOCKET
> - LANDLOCK_SCOPE_SIGNAL

> https://docs.kernel.org/userspace-api/landlock.html#ipc-scoping

> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> Andrea Cervesato (4):
>       Add landlock ABI v6 fallback
>       landlock02: support landlock ABI v6
>       landlock: add landlock09 test
>       landlock: add landlock10 test

>  include/lapi/landlock.h                            |  23 +++-
>  testcases/kernel/syscalls/landlock/.gitignore      |   2 +
>  testcases/kernel/syscalls/landlock/landlock02.c    |  10 +-
>  testcases/kernel/syscalls/landlock/landlock09.c    | 132 +++++++++++++++++++++
>  testcases/kernel/syscalls/landlock/landlock10.c    | 110 +++++++++++++++++
>  .../kernel/syscalls/landlock/landlock_common.h     |  11 ++
>  6 files changed, 280 insertions(+), 8 deletions(-)

           reply	other threads:[~2025-03-27 13:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250327-landlock_unix_socket-v1-0-584653f66d9c@suse.com>]

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=20250327131838.GB77751@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.de \
    --cc=gnoack@google.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=mic@digikod.net \
    /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