All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
Cc: audit@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH 4/4] landlock: Document namespace denial operations
Date: Tue, 17 Nov 2026 10:24:13 +0000	[thread overview]
Message-ID: <sashiko-outbox-218608@kernel.org> (raw)
In-Reply-To: <20261117102110.2524197-5-mic@digikod.net>

> Namespace denial records now distinguish creation from entry.  Document
> the namespace_op field in the audit and trace references, and clarify
> that it describes the semantic namespace hook rather than exact syscall
> provenance.
> 
> Creation reports the ID allocated for a namespace that never becomes
> reachable, whereas entry reports the existing target ID.
> 
> Cc: Günther Noack <gnoack@google.com>
> Signed-off-by: Mickaël Salaün <mic@digikod.net>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261117102110.2524197-1-mic@digikod.net?part=4


      reply	other threads:[~2026-11-17 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 10:21 [PATCH 0/4] Landlock: Fix namespace and capability denials Mickaël Salaün
2026-11-17 10:21 ` [PATCH 1/4] landlock: Distinguish namespace creation and entry denials Mickaël Salaün
2026-11-17 10:29   ` sashiko-bot
2026-11-17 10:21 ` [PATCH 2/4] landlock: Add capability objects to denial tracing Mickaël Salaün
2026-11-17 10:27   ` sashiko-bot
2026-11-17 10:21 ` [PATCH 3/4] selftests/landlock: Test namespace denial operations Mickaël Salaün
2026-11-17 10:24   ` sashiko-bot
2026-11-17 10:21 ` [PATCH 4/4] landlock: Document " Mickaël Salaün
2026-11-17 10:24   ` sashiko-bot [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=sashiko-outbox-218608@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=audit@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.