From: "Günther Noack" <gnoack3000@gmail.com>
To: "Alejandro Colomar" <alx@kernel.org>, "Mickaël Salaün" <mic@digikod.net>
Cc: linux-man@vger.kernel.org, "Günther Noack" <gnoack3000@gmail.com>
Subject: [PATCH v2 1/4] man/man2/landlock_create_ruleset.2: Document EINVAL scope case
Date: Tue, 21 Apr 2026 00:35:14 +0200 [thread overview]
Message-ID: <20260420223517.8020-2-gnoack3000@gmail.com> (raw)
In-Reply-To: <20260420223517.8020-1-gnoack3000@gmail.com>
This brings the manpage in-line with the kernel documentation. Here,
"scope" is a field in the passed struct landlock_ruleset_access, which
can result in EINVAL if populated improperly.
Signed-off-by: Günther Noack <gnoack3000@gmail.com>
---
man/man2/landlock_create_ruleset.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man2/landlock_create_ruleset.2 b/man/man2/landlock_create_ruleset.2
index 5d64f4c2862c..d4eb5d827656 100644
--- a/man/man2/landlock_create_ruleset.2
+++ b/man/man2/landlock_create_ruleset.2
@@ -156,7 +156,7 @@ was not a valid address.
.B EINVAL
Unknown
.IR flags ,
-or unknown access, or too small
+or unknown access, or unknown scope, or too small
.IR size .
.TP
.B ENOMSG
--
2.53.0
next prev parent reply other threads:[~2026-04-20 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 22:35 [PATCH v2 0/4] Update Landlock docs to Landlock ABI v8 Günther Noack
2026-04-20 22:35 ` Günther Noack [this message]
2026-04-21 0:19 ` [PATCH v2 1/4] man/man2/landlock_create_ruleset.2: Document EINVAL scope case Alejandro Colomar
2026-04-20 22:35 ` [PATCH v2 2/4] man/man[27]/{landlock_create_ruleset.2,landlock.7}: Document LANDLOCK_CREATE_RULESET_ERRATA Günther Noack
2026-04-21 0:16 ` Alejandro Colomar
2026-04-21 17:58 ` Günther Noack
2026-04-20 22:35 ` [PATCH v2 3/4] man/man[27]/{landlock_restrict_self.2,landlock.7}: Document LANDLOCK_RESTRICT_SELF_TSYNC (ABI v8) Günther Noack
2026-04-20 22:35 ` [PATCH v2 4/4] man/man2/landlock_restrict_self.2: Document ABI requirement for logging flags Günther Noack
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=20260420223517.8020-2-gnoack3000@gmail.com \
--to=gnoack3000@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--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