From: "Mickaël Salaün" <mic@digikod.net>
To: Samasth Norway Ananda <samasth.norway.ananda@oracle.com>
Cc: gnoack@google.com, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] landlock: documentation improvements
Date: Thu, 5 Feb 2026 20:23:20 +0100 [thread overview]
Message-ID: <20260205.Ohrao7yiegai@digikod.net> (raw)
In-Reply-To: <20260128031814.2945394-1-samasth.norway.ananda@oracle.com>
Thanks for these improvements, it helps! I'll send these changes for
Linux 7.0
On Tue, Jan 27, 2026 at 07:18:09PM -0800, Samasth Norway Ananda wrote:
> This patch series improves Landlock documentation by addressing gaps in
> ABI compatibility examples, adding errata documentation, and documenting
> the audit blockers field format.
>
> Changes since v2:
> =================
>
> Patch 1/3:
> - Handle restrict_flags in a separate code block, not in the switch
> - Clear all three ABI v7 logging flags for a generic example
> - Reference sys_landlock_restrict_self() for available flags
> - Use restrict_flags in landlock_restrict_self()
>
> Patch 2/3:
> - Use kernel-doc directives to include errata from header files
> - Move rephrased ABI version text before errata section
>
> Patch 3/3:
> - No changes
>
> Changes since v1:
> =================
>
> Patch 1/3:
> - Add backwards compatibility section for restrict flags
> - Fix /usr rule description
>
> Patch 2/3:
> - Enhance existing DOC sections with Impact descriptions
> - Add errata usage documentation
>
> Patch 3/3:
> - Document audit blocker field format
>
> Samasth Norway Ananda (3):
> landlock: add backwards compatibility for restrict flags
> landlock: add errata documentation section
> landlock: document audit blockers field format
>
> Documentation/admin-guide/LSM/landlock.rst | 20 ++++-
> Documentation/userspace-api/landlock.rst | 97 +++++++++++++++++++---
> security/landlock/errata/abi-1.h | 8 ++
> security/landlock/errata/abi-4.h | 7 ++
> security/landlock/errata/abi-6.h | 10 +++
> security/landlock/syscalls.c | 4 +-
> 6 files changed, 131 insertions(+), 15 deletions(-)
>
> --
> 2.50.1
>
>
prev parent reply other threads:[~2026-02-05 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 3:18 [PATCH v3 0/3] landlock: documentation improvements Samasth Norway Ananda
2026-01-28 3:18 ` [PATCH v3 1/3] landlock: add backwards compatibility for restrict flags Samasth Norway Ananda
2026-02-01 12:24 ` Günther Noack
2026-01-28 3:18 ` [PATCH v3 2/3] landlock: add errata documentation section Samasth Norway Ananda
2026-02-01 12:23 ` Günther Noack
2026-01-28 3:18 ` [PATCH v3 3/3] landlock: Document audit blocker field format Samasth Norway Ananda
2026-02-05 19:23 ` 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=20260205.Ohrao7yiegai@digikod.net \
--to=mic@digikod.net \
--cc=gnoack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=samasth.norway.ananda@oracle.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