public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Günther Noack" <gnoack3000@gmail•com>
To: Justin Suess <utilityemal77@gmail•com>
Cc: "Mickaël Salaün" <mic@digikod•net>,
	"Paul Moore" <paul@paul-moore•com>,
	"James Morris" <jmorris@namei•org>,
	"Serge E . Hallyn" <serge@hallyn•com>,
	linux-security-module@vger•kernel.org,
	"Tingmao Wang" <m@maowtm•org>,
	"Samasth Norway Ananda" <samasth.norway.ananda@oracle•com>,
	"Matthieu Buffet" <matthieu@buffet•re>,
	"Mikhail Ivanov" <ivanov.mikhail1@huawei-partners•com>,
	konstantin.meskhidze@huawei•com,
	"Demi Marie Obenour" <demiobenour@gmail•com>,
	"Alyssa Ross" <hi@alyssa•is>, "Jann Horn" <jannh@google•com>,
	"Tahera Fahimi" <fahimitahera@gmail•com>,
	"Simon Horman" <horms@kernel•org>,
	netdev@vger•kernel.org,
	"Alexander Viro" <viro@zeniv•linux.org.uk>,
	"Christian Brauner" <brauner@kernel•org>
Subject: Re: [PATCH v2 1/5] lsm: Add hook unix_path_connect
Date: Sun, 11 Jan 2026 10:55:27 +0100	[thread overview]
Message-ID: <20260111.ac6689582f41@gnoack.org> (raw)
In-Reply-To: <4bc22faa-2927-4ef9-b5dc-67a7575177e9@gmail.com>

On Sat, Jan 10, 2026 at 11:45:03AM -0500, Justin Suess wrote:
> Just for awareness,
> 
> I'm considering renaming this hook to unix_socket_path_lookup, since as Günther
> pointed out this hook is not just hit on connect, but also on sendmsg.

+1 I would be in favor of this.

(In doubt, Paul Moore has the last word on LSM hook naming.  I believe
that both "lookup" and "resolve" are being used exchangeably to refer
to path lookups. (e.g. see the path_resolution(7) man page [1]))

–Günther

[1] https://man7.org/linux/man-pages/man7/path_resolution.7.html

  reply	other threads:[~2026-01-11  9:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-10 14:32 [PATCH v2 0/5] landlock: Pathname-based UNIX connect() control Günther Noack
2026-01-10 14:32 ` [PATCH v2 1/5] lsm: Add hook unix_path_connect Günther Noack
2026-01-10 16:45   ` Justin Suess
2026-01-11  9:55     ` Günther Noack [this message]
2026-01-13 22:51     ` Paul Moore
2026-01-13 23:30       ` Paul Moore
2026-01-13  9:34   ` Christian Brauner
2026-01-13 23:27     ` Paul Moore
2026-01-15 10:10       ` Günther Noack
2026-01-15 21:24         ` Demi Marie Obenour
2026-01-15 22:32           ` Günther Noack
2026-01-15 21:46         ` Paul Moore
2026-01-12 16:08 ` [PATCH v2 0/5] landlock: Pathname-based UNIX connect() control Mickaël Salaün
2026-01-12 20:53   ` Günther Noack
2026-01-17 18:57     ` Justin Suess
2026-01-18 17:44       ` 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=20260111.ac6689582f41@gnoack.org \
    --to=gnoack3000@gmail$(echo .)com \
    --cc=brauner@kernel$(echo .)org \
    --cc=demiobenour@gmail$(echo .)com \
    --cc=fahimitahera@gmail$(echo .)com \
    --cc=hi@alyssa$(echo .)is \
    --cc=horms@kernel$(echo .)org \
    --cc=ivanov.mikhail1@huawei-partners$(echo .)com \
    --cc=jannh@google$(echo .)com \
    --cc=jmorris@namei$(echo .)org \
    --cc=konstantin.meskhidze@huawei$(echo .)com \
    --cc=linux-security-module@vger$(echo .)kernel.org \
    --cc=m@maowtm$(echo .)org \
    --cc=matthieu@buffet$(echo .)re \
    --cc=mic@digikod$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=paul@paul-moore$(echo .)com \
    --cc=samasth.norway.ananda@oracle$(echo .)com \
    --cc=serge@hallyn$(echo .)com \
    --cc=utilityemal77@gmail$(echo .)com \
    --cc=viro@zeniv$(echo .)linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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