From: "Mickaël Salaün" <mic@digikod.net>
To: Tingmao Wang <m@maowtm.org>
Cc: "Günther Noack" <gnoack@google.com>,
"Daniel Burgener" <dburgener@linux.microsoft.com>,
"Jann Horn" <jannh@google.com>, "Jeff Xu" <jeffxu@google.com>,
"Kees Cook" <kees@kernel.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Matthieu Buffet" <matthieu@buffet.re>,
"Mikhail Ivanov" <ivanov.mikhail1@huawei-partners.com>,
"Ryan Sullivan" <rysulliv@redhat.com>,
"Shervin Oloumi" <enlightened@google.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
linux-security-module@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1 1/5] landlock: Rename landlock_id to landlock_rule_ref
Date: Tue, 27 May 2025 16:53:08 +0200 [thread overview]
Message-ID: <20250527.AhJ9Wuuc8vee@digikod.net> (raw)
In-Reply-To: <112ec51d-523b-444b-ad7e-7b1b3d56507c@maowtm.org>
On Mon, May 26, 2025 at 07:38:00PM +0100, Tingmao Wang wrote:
> On 5/23/25 17:57, Mickaël Salaün wrote:
> > [RFC PATCH v1 1/5] landlock: Rename landlock_id to landlock_rule_ref
> >
> > This avoids confusion with the new Landlock IDs.
>
> A very very minor suggestion, but I think to someone new, landlock_rule_ref
> would sound like a reference to a specific rule (like a *struct
> landlock_rule), but really it represents the "name", or in fact, target of a
> rule... Maybe we should call it "landlock_rule_target"?
>
> (Or maybe the confusion is resolved quickly when they look at the definition
> so maybe it doesn't matter)
You're right that the name is confusing. What about just struct
landlock_reference? Such structure do reference an element (an object
or a raw value), which might be in a ruleset, a domain, or none of them.
We should also probably use "ref=" instead of "object=" in the trace
event.
>
> >
> > TODO: Split in several commits to ease potential backports according to
> > stable branches
> >
> > Cc: Günther Noack <gnoack@google.com>
> > Signed-off-by: Mickaël Salaün <mic@digikod.net>
> > ---
> [...]
>
next prev parent reply other threads:[~2025-05-27 14:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 16:57 [RFC PATCH v1 0/5] Landlock tracepoints Mickaël Salaün
2025-05-23 16:57 ` [RFC PATCH v1 1/5] landlock: Rename landlock_id to landlock_rule_ref Mickaël Salaün
2025-05-26 18:38 ` Tingmao Wang
2025-05-27 14:53 ` Mickaël Salaün [this message]
2025-05-23 16:57 ` [RFC PATCH v1 2/5] landlock: Merge landlock_find_rule() into landlock_unmask_layers() Mickaël Salaün
2025-05-26 18:38 ` Tingmao Wang
2025-05-27 14:53 ` Mickaël Salaün
2025-05-23 16:57 ` [RFC PATCH v1 3/5] tracing: Add __print_untrusted_str() Mickaël Salaün
2025-05-23 18:22 ` Steven Rostedt
2025-05-26 17:46 ` Mickaël Salaün
2025-05-23 16:57 ` [RFC PATCH v1 4/5] landlock: Add landlock_add_rule_fs tracepoint Mickaël Salaün
2025-05-26 18:37 ` Tingmao Wang
2025-05-27 14:53 ` Mickaël Salaün
2025-05-23 16:57 ` [RFC PATCH v1 5/5] landlock: Add landlock_check_rule tracepoint Mickaël Salaün
2025-05-26 18:37 ` [RFC PATCH v1 0/5] Landlock tracepoints Tingmao Wang
2025-05-27 14:52 ` Mickaël Salaün
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=20250527.AhJ9Wuuc8vee@digikod.net \
--to=mic@digikod.net \
--cc=dburgener@linux.microsoft.com \
--cc=enlightened@google.com \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=jannh@google.com \
--cc=jeffxu@google.com \
--cc=kees@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=m@maowtm.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=matthieu@buffet.re \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rysulliv@redhat.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;
as well as URLs for NNTP newsgroup(s).