From: Johan Hovold <johan@kernel.org>
To: Kuniyuki Iwashima <kuni1840@gmail.com>
Cc: "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>,
"Kuniyuki Iwashima" <kuniyu@google.com>,
"Christian Heusel" <christian@heusel.eu>,
"André Almeida" <andrealmeid@igalia.com>,
netdev@vger.kernel.org, "Jacek Łuczak" <difrost.kernel@gmail.com>
Subject: Re: [PATCH v1 net] af_unix: Allow passing cred for embryo without SO_PASSCRED/SO_PASSPIDFD.
Date: Mon, 16 Jun 2025 16:09:29 +0200 [thread overview]
Message-ID: <aFAlmTEPUqBdTJJ6@hovoldconsulting.com> (raw)
In-Reply-To: <20250611202758.3075858-1-kuni1840@gmail.com>
On Wed, Jun 11, 2025 at 01:27:35PM -0700, Kuniyuki Iwashima wrote:
> From: Kuniyuki Iwashima <kuniyu@google.com>
>
> Before the cited commit, the kernel unconditionally embedded SCM
> credentials to skb for embryo sockets even when both the sender
> and listener disabled SO_PASSCRED and SO_PASSPIDFD.
>
> Now, the credentials are added to skb only when configured by the
> sender or the listener.
>
> However, as reported in the link below, it caused a regression for
> some programs that assume credentials are included in every skb,
> but sometimes not now.
>
> The only problematic scenario would be that a socket starts listening
> before setting the option. Then, there will be 2 types of non-small
> race window, where a client can send skb without credentials, which
> the peer receives as an "invalid" message (and aborts the connection
> it seems ?):
>
> Client Server
> ------ ------
> s1.listen() <-- No SO_PASS{CRED,PIDFD}
> s2.connect()
> s2.send() <-- w/o cred
> s1.setsockopt(SO_PASS{CRED,PIDFD})
> s2.send() <-- w/ cred
>
> or
>
> Client Server
> ------ ------
> s1.listen() <-- No SO_PASS{CRED,PIDFD}
> s2.connect()
> s2.send() <-- w/o cred
> s3, _ = s1.accept() <-- Inherit cred options
> s2.send() <-- w/o cred but not set yet
>
> s3.setsockopt(SO_PASS{CRED,PIDFD})
> s2.send() <-- w/ cred
>
> It's unfortunate that buggy programs depend on the behaviour,
> but let's restore the previous behaviour.
For the record, this one fixes the wlroots and Xorg crashes on USB-C
DisplayPort Altmode hotplug that I hit consistently with 6.16-rc1 on
machines like the Lenovo ThinkPad X13s and T14s.
> Fixes: 3f84d577b79d ("af_unix: Inherit sk_flags at connect().")
> Reported-by: Jacek Łuczak <difrost.kernel@gmail.com>
> Closes: https://lore.kernel.org/all/68d38b0b-1666-4974-85d4-15575789c8d4@gmail.com/
> Signed-off-by: Kuniyuki Iwashima <kuniyu@google.com>
Johan
prev parent reply other threads:[~2025-06-16 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 20:27 [PATCH v1 net] af_unix: Allow passing cred for embryo without SO_PASSCRED/SO_PASSPIDFD Kuniyuki Iwashima
2025-06-11 21:03 ` Christian Heusel
2025-06-11 22:56 ` André Almeida
2025-06-12 12:11 ` Jacek Łuczak
2025-06-12 15:20 ` patchwork-bot+netdevbpf
2025-06-16 14:09 ` Johan Hovold [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=aFAlmTEPUqBdTJJ6@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andrealmeid@igalia.com \
--cc=christian@heusel.eu \
--cc=davem@davemloft.net \
--cc=difrost.kernel@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--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;
as well as URLs for NNTP newsgroup(s).