From: "Günther Noack" <gnoack@google.com>
To: "Alejandro Colomar" <alx@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Tahera Fahimi" <fahimitahera@gmail.com>
Cc: "Günther Noack" <gnoack@google.com>,
"Tanya Agarwal" <tanyaagarwal25699@gmail.com>,
linux-security-module@vger.kernel.org, linux-man@vger.kernel.org,
"Daniel Burgener" <dburgener@linux.microsoft.com>
Subject: [PATCH man v3 1/2] landlock.7: Copy introductory description of Landlock rules
Date: Mon, 3 Mar 2025 20:50:29 +0100 [thread overview]
Message-ID: <20250303195056.136777-2-gnoack@google.com> (raw)
In-Reply-To: <20250303194510.135506-2-gnoack@google.com>
Copy over the existing wording from kernel documentation, as it was introduced
in Linux commit 51442e8d64bc ("landlock: Document network support"). Landlock
rules are not only about the filesystem any more and the new wording is more
appropriate.
Signed-off-by: Günther Noack <gnoack@google.com>
---
man/man7/landlock.7 | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/man/man7/landlock.7 b/man/man7/landlock.7
index c6b7272ea..7b7a797ad 100644
--- a/man/man7/landlock.7
+++ b/man/man7/landlock.7
@@ -39,13 +39,23 @@ the running kernel must support Landlock and
it must be enabled at boot time.
.\"
.SS Landlock rules
-A Landlock rule describes an action on an object.
-An object is currently a file hierarchy,
-and the related filesystem actions are defined with access rights (see
-.BR landlock_add_rule (2)).
+A Landlock rule describes an action on an object
+which the process intends to perform.
A set of rules is aggregated in a ruleset,
which can then restrict the thread enforcing it,
and its future children.
+.P
+The two existing types of rules are:
+.TP
+.B Filesystem rules
+For these rules, the object is a file hierarchy,
+and the related filesystem actions are defined with
+.IR "filesystem access rights" .
+.TP
+.BR "Network rules" " (since ABI v4)"
+For these rules, the object is a TCP port,
+and the related actions are defined with
+.IR "network access rights" .
.\"
.SS Filesystem actions
These flags enable to restrict a sandboxed process to a
--
2.48.1.711.g2feabab25a-goog
next parent reply other threads:[~2025-03-03 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250303194510.135506-2-gnoack@google.com>
2025-03-03 19:50 ` Günther Noack [this message]
2025-03-05 18:35 ` [PATCH man v3 1/2] landlock.7: Copy introductory description of Landlock rules Alejandro Colomar
2025-03-03 19:50 ` [PATCH man v3 2/2] landlock.7: Add IPC scoping documentation in line with kernel side 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=20250303195056.136777-2-gnoack@google.com \
--to=gnoack@google.com \
--cc=alx@kernel.org \
--cc=dburgener@linux.microsoft.com \
--cc=fahimitahera@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=tanyaagarwal25699@gmail.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