From: Christian Brauner <brauner@kernel.org>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: Christian Brauner <brauner@kernel.org>,
Aleksa Sarai <cyphar@cyphar.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 3/5] net: af_unix: useful handling of LSM denials on SCM_RIGHTS
Date: Wed, 01 Jul 2026 09:44:05 +0200 [thread overview]
Message-ID: <20260701-angezapft-unreflektiert-galant-e89d63be60ac@brauner> (raw)
In-Reply-To: <158151977.3525022.1782821834050@kpc.webmail.kpnmail.nl>
> I also choose to not put -EPERM as sentinel as suggested first, but use the
> actual LSM error. Agreed?
Yes. We have to surface the actual error. In case the LSM is returning
some custom error (can easily happen from a bpf lsm).
next prev parent reply other threads:[~2026-07-01 7:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 19:43 [PATCH net-next v3 0/5] " Jori Koolstra
2026-06-29 19:43 ` [PATCH net-next v3 1/5] net: scm: move scm_detach_fds() from common path to scm_recv_unix() Jori Koolstra
2026-06-29 19:43 ` [PATCH net-next v3 2/5] vfs: add function receive_fd_filtered() that makes LSM filtering explicit Jori Koolstra
2026-06-29 19:43 ` [PATCH net-next v3 3/5] net: af_unix: useful handling of LSM denials on SCM_RIGHTS Jori Koolstra
2026-06-30 9:58 ` Christian Brauner
2026-06-30 12:17 ` Jori Koolstra
2026-07-01 7:44 ` Christian Brauner [this message]
2026-06-30 16:43 ` Kuniyuki Iwashima
2026-06-29 19:43 ` [PATCH net-next v3 4/5] net: af_unix: replace copy_from_sockptr() with copy_safe_from_sockptr() Jori Koolstra
2026-06-30 16:18 ` Kuniyuki Iwashima
2026-06-29 19:43 ` [PATCH net-next v3 5/5] selftest: Add tests for useful handling of LSM denials on SCM_RIGHTS Jori Koolstra
2026-06-30 14:17 ` Jakub Kicinski
2026-06-30 14:35 ` Jori Koolstra
2026-06-30 16:23 ` Kuniyuki Iwashima
2026-07-01 7:38 ` Christian Brauner
2026-07-01 9:31 ` Jori Koolstra
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=20260701-angezapft-unreflektiert-galant-e89d63be60ac@brauner \
--to=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jkoolstra@xs4all.nl \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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