From: Kuniyuki Iwashima <kuniyu@google.com>
To: brian.scott.sampson@gmail.com
Cc: christian@heusel.eu, davem@davemloft.net,
difrost.kernel@gmail.com, dnaim@cachyos.org,
edumazet@google.com, horms@kernel.org, kuba@kernel.org,
kuni1840@gmail.com, kuniyu@google.com,
linux-kernel@vger.kernel.org, mario.limonciello@amd.com,
netdev@vger.kernel.org, pabeni@redhat.com,
regressions@lists.linux.dev
Subject: Re: [REGRESSION] af_unix: Introduce SO_PASSRIGHTS - break OpenGL
Date: Sat, 20 Sep 2025 03:50:43 +0000 [thread overview]
Message-ID: <20250920035146.2149127-1-kuniyu@google.com> (raw)
In-Reply-To: <caa08e5b15bc35b9f3c24f679c62ded1e8e58925.camel@gmail.com>
From: brian.scott.sampson@gmail.com
Date: Wed, 17 Sep 2025 15:25:07 -0500
> > Thanks for testing the painful scenario.
> >
> > Could you apply this on top of the previous diff and give it
> > another shot ?
> >
> > I think the application hit a race similar to one in 43fb2b30eea7.
> Just tested again with latest mainline, but no change. Once suspended,
> keyboard becomes inactive and no longer accepts any input, so no way to
> switch to tty to view dmesg. The only way to move forward after
> suspending is holding down power to hard shutdown, then power back on.
> I tried enabling persistence in the systemd journal, then checking
> journalctl -k -b -1, but nothing is recorded from dmesg after the
> suspend.
Thank you for your patience.
I assumed SO_PASSCRED was the problem, but I missed
SO_PASSCRED was also inherited durint accept().
Could you apply this on top of the previous changes ?
Also, could you tell what desktop manager and distro
you are using ? If this attempt fails, I'll try to
reproduce with the same version on my desktop.
---8<---
diff --git a/include/net/sock.h b/include/net/sock.h
index 211084602e01..b61d4fdb7fc4 100644
--- a/include/net/sock.h
+++ b/include/net/sock.h
@@ -541,7 +541,8 @@ struct sock {
sk_scm_rights : 1,
sk_scm_embryo_cred: 1,
sk_scm_parent_cred: 1,
- sk_scm_unused : 2;
+ sk_scm_parent_sec: 1,
+ sk_scm_unused : 1;
};
};
u8 sk_clockid;
diff --git a/net/core/scm.c b/net/core/scm.c
index e603bf5400e0..359d56d454b4 100644
--- a/net/core/scm.c
+++ b/net/core/scm.c
@@ -435,7 +435,8 @@ static void scm_passec(struct sock *sk, struct msghdr *msg, struct scm_cookie *s
struct lsm_context ctx;
int err;
- if (sk->sk_scm_security) {
+ if (sk->sk_scm_security || sk->sk_scm_parent_sec) {
+ WARN_ON_ONCE(!sk->sk_scm_security);
err = security_secid_to_secctx(scm->secid, &ctx);
if (err >= 0) {
@@ -449,7 +450,7 @@ static void scm_passec(struct sock *sk, struct msghdr *msg, struct scm_cookie *s
static bool scm_has_secdata(struct sock *sk)
{
- return sk->sk_scm_security;
+ return sk->sk_scm_security || sk->sk_scm_parent_sec;
}
#else
static void scm_passec(struct sock *sk, struct msghdr *msg, struct scm_cookie *scm)
diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
index b6ff7ad0443a..a35082269990 100644
--- a/net/unix/af_unix.c
+++ b/net/unix/af_unix.c
@@ -1899,6 +1899,7 @@ static int unix_accept(struct socket *sock, struct socket *newsock,
unix_update_edges(unix_sk(tsk));
newsock->state = SS_CONNECTED;
tsk->sk_scm_parent_cred = sk->sk_scm_credentials;
+ tsk->sk_scm_parent_sec = sk->sk_scm_security;
sock_graft(tsk, newsock);
unix_state_unlock(tsk);
return 0;
---8<---
next prev parent reply other threads:[~2025-09-20 3:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 19:22 Jacek Łuczak
2025-06-11 11:46 ` Christian Heusel
2025-06-11 16:42 ` Kuniyuki Iwashima
2025-06-11 17:10 ` Christian Heusel
2025-06-11 19:24 ` André Almeida
2025-06-18 7:30 ` Matthew Schwartz
2025-09-16 22:16 ` brian.scott.sampson
2025-09-17 1:33 ` Kuniyuki Iwashima
2025-09-17 14:40 ` brian.scott.sampson
2025-09-17 18:42 ` Kuniyuki Iwashima
2025-09-17 20:25 ` brian.scott.sampson
2025-09-20 3:50 ` Kuniyuki Iwashima [this message]
2025-09-20 22:28 ` brian.scott.sampson
2025-11-09 16:07 ` brian.scott.sampson
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=20250920035146.2149127-1-kuniyu@google.com \
--to=kuniyu@google.com \
--cc=brian.scott.sampson@gmail.com \
--cc=christian@heusel.eu \
--cc=davem@davemloft.net \
--cc=difrost.kernel@gmail.com \
--cc=dnaim@cachyos.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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®