mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: brauner@kernel.org, cyphar@cyphar.com, kuniyu@google.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/4] net: af_unix: useful handling of LSM denials on SCM_RIGHTS
Date: Tue, 18 Aug 2026 01:30:20 +0000	[thread overview]
Message-ID: <178701662063.1820167.14677074297106840300.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813162818.149248-1-jkoolstra@xs4all.nl>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 13 Aug 2026 12:28:14 -0400 you wrote:
> Right now if some LSM denies an AF_UNIX socket peer to receive a
> SCM_RIGHTS fd, the SCM_RIGHTS fd array will be cut short at
> that point, and MSG_CTRUNC is set on return of recvmsg(2). This is
> highly problematic behaviour, because it leaves the receiver
> wondering what happened. As per man page MSG_CTRUNC is supposed to
> indicate that the control buffer was sized too short, but suddenly
> a permission error might result in the exact same flag being set.
> Moreover, the receiver has no chance to determine how many fds got
> originally sent and how many were suppressed.[1]
> 
> [...]

Here is the summary with links:
  - [net-next,v7,1/4] net: af_unix: enable custom setsockopt for all socket types
    https://git.kernel.org/netdev/net-next/c/de1c489b57c1
  - [net-next,v7,2/4] net: scm: move scm_detach_fds() from common path to scm_recv_unix()
    https://git.kernel.org/netdev/net-next/c/48b84acc5e18
  - [net-next,v7,3/4] net: af_unix: useful handling of LSM denials on SCM_RIGHTS
    https://git.kernel.org/netdev/net-next/c/fd8756fa1487
  - [net-next,v7,4/4] selftest: Add tests for useful handling of LSM denials on SCM_RIGHTS
    https://git.kernel.org/netdev/net-next/c/5d513ce19de9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-18  1:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 16:28 Jori Koolstra
2026-08-13 16:28 ` [PATCH net-next v7 1/4] net: af_unix: enable custom setsockopt for all socket types Jori Koolstra
2026-08-13 16:28 ` [PATCH net-next v7 2/4] net: scm: move scm_detach_fds() from common path to scm_recv_unix() Jori Koolstra
2026-08-13 16:28 ` [PATCH net-next v7 3/4] net: af_unix: useful handling of LSM denials on SCM_RIGHTS Jori Koolstra
2026-08-13 16:45 ` [PATCH net-next v7 0/4] " Jori Koolstra
2026-08-14 17:18   ` Jakub Kicinski
2026-08-14 17:32     ` Jori Koolstra
2026-08-14 18:45       ` Jakub Kicinski
2026-08-14 17:28 ` [PATCH net-next v7 4/4] selftest: Add tests for " Jori Koolstra
2026-08-18  1:30 ` patchwork-bot+netdevbpf [this message]

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=178701662063.1820167.14677074297106840300.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=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

all inboxes | Powered by JetHome®