netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: brian.scott.sampson@gmail.com
To: Kuniyuki Iwashima <kuniyu@google.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, 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 17:28:40 -0500	[thread overview]
Message-ID: <6980dba4ac0be1d6bbed8cb595d38114d89a14f5.camel@gmail.com> (raw)
In-Reply-To: <20250920035146.2149127-1-kuniyu@google.com>

> 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.

No worries! I just applied this patch as well(on top of the other two
in the order you originally provided), and still seeing the black
screen upon resume. I am seeing a stack trace now when I check
systemd's journal, which wasn't there before(not sure if its related).
I do have the System.map as well for this build, but not sure why
everything seemed to end up so cryptic. I'll paste it below as well as
my desktop: 

Desktop Environment: Gnome 48.5 
Window Manager: Mutter (Wayland) 
Distribution: CachyOS


Trace:

❯ sudo journalctl -k -b -1 | grep "cut here" -A52 | awk -F 'kernel: '
'{print $2}'
------------[ cut here ]------------
WARNING: CPU: 3 PID: 545 at net/core/sock.c:1548
sk_setsockopt+0x1709/0x1b50
Modules linked in: dm_mod crypto_user loop nfnetlink lz4 zram
842_decompress lz4hc_compress 842_compress lz4_compress amdgpu amdxcp
i2c_algo_bit drm_ttm_helper ttm drm_exec gpu_sched drm_suballoc_helper
video rtsx_pci_sdmmc mmc_core drm_panel_backlight_quirks nvme drm_buddy
nvme_core drm_display_helper serio_raw rtsx_pci nvme_keyring cec
nvme_auth wmi
CPU: 3 UID: 0 PID: 545 Comm: systemd-journal Not tainted 6.17.0-rc6-
local-00268-g3b08f56fbbb9-dirty #1 PREEMPT(full) 
c74d467c5c838be6e0491dc375b7e67fc07dfcf3
Hardware name: Alienware Alienware m18 R1 AMD/0HR91K, BIOS 1.19.0
07/01/2025
RIP: 0010:sk_setsockopt+0x1709/0x1b50
Code: 00 e9 30 eb ff ff ba a1 ff ff ff e9 64 eb ff ff 0f b6 43 12 3c 0a
0f 85 d0 f3 ff ff 8b 83 b8 00 00 00 85 c0 0f 84 c2 f3 ff ff <0f> 0b e9
bb f3 ff ff 48 8d 7c 24 38 b9 08 00 00 00 4c 89 de 4c 89
RSP: 0018:ffffccbfc3e8bbf8 EFLAGS: 00010202
RAX: 0000000000000010 RBX: ffff8a3598268cc0 RCX: ffff8a35805db400
RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffffffffadc442f3
RBP: ffffccbfc3e8bc98 R08: ffff8a35c4ed8000 R09: 0000000000000004
R10: 0000000000000010 R11: 00007ffeb08dc62c R12: 0000000000000000
R13: 0000000000000001 R14: 0000000000000001 R15: ffffccbfc3e8bd30
FS:  00007f47de2c7880(0000) GS:ffff8a3d0dc30000(0000)
knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f47de0bb910 CR3: 000000011431b000 CR4: 0000000000f50ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? __x64_sys_fcntl+0x80/0x110
 unix_setsockopt+0x42/0xd0
 ? security_socket_setsockopt+0x52/0x160
 do_sock_setsockopt+0xb2/0x190
 ? __seccomp_filter+0x41/0x4e0
 __sys_setsockopt+0x7b/0xc0
 __x64_sys_setsockopt+0x1f/0x30
 do_syscall_64+0x81/0x970
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? do_syscall_64+0x81/0x970
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? do_sock_getsockopt+0x1cc/0x210
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __sys_getsockopt+0x77/0xc0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? do_syscall_64+0x81/0x970
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? do_syscall_64+0x81/0x970
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? exc_page_fault+0x7e/0x1a0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7f47ddb42b4e
Code: 48 83 ec 10 48 63 c9 48 63 ff 45 89 c9 6a 2c e8 48 39 f6 ff 48 83
c4 18 c3 0f 1f 00 f3 0f 1e fa 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 0a c3 66 0f 1f 84 00 00 00 00 00 48 8b 15 81
RSP: 002b:00007ffeb08dc618 EFLAGS: 00000202 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 000055798b740c40 RCX: 00007f47ddb42b4e
RDX: 0000000000000010 RSI: 0000000000000001 RDI: 0000000000000005
RBP: 00007ffeb08dc630 R08: 0000000000000004 R09: 0000000000000000
R10: 00007ffeb08dc62c R11: 0000000000000202 R12: 0000000000000005
R13: 00007ffeb08dc6d0 R14: 0000000000000006 R15: 0000000000000000
 </TASK>
---[ end trace 0000000000000000 ]---





  reply	other threads:[~2025-09-20 22:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <68d38b0b-1666-4974-85d4-15575789c8d4@gmail.com>
2025-06-11 11:46 ` [REGRESSION] af_unix: Introduce SO_PASSRIGHTS - break OpenGL 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
2025-09-20 22:28                 ` brian.scott.sampson [this message]
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=6980dba4ac0be1d6bbed8cb595d38114d89a14f5.camel@gmail.com \
    --to=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=kuniyu@google.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;
as well as URLs for NNTP newsgroup(s).