* [moderation/CI] Re: net: support thread-specific pidfds for send and connect
@ 2026-08-31 13:22 syzbot ci
0 siblings, 0 replies; only message in thread
From: syzbot ci @ 2026-08-31 13:22 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v1] net: support thread-specific pidfds for send and connect
https://lore.kernel.org/all/20260831-work-unix-passpidfd-v1-0-70cbfda0c7ba@kernel.org
* [PATCH 01/10] pid: add helpers to operate on a struct pid array
* [PATCH 02/10] af_unix: record the pid of the sending thread
* [PATCH 03/10] net: add SO_PASSPIDFD_THREAD to get a thread-specific SCM_PIDFD
* [PATCH 04/10] selftests/net: SO_PASSPIDFD_THREAD
* [PATCH 05/10] net: turn sk_peer_pid into an array indexed by pid type
* [PATCH 06/10] af_unix: record the pid of the connecting thread
* [PATCH 07/10] net: add SO_PEERPIDFD_THREAD to get a thread-specific pidfd
* [PATCH 08/10] selftests/net: SO_PEERPIDFD_THREAD
* [PATCH 09/10] pidfs: record the coredump on the dumping thread's pid too
* [PATCH 10/10] selftests/coredump: check the dumping thread's pidfd
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/524fcdbe-c7b4-4e1d-b6d3-52ea41fd5526
***
kernel build error
tree: drm-next
URL: https://gitlab.freedesktop.org/drm/kernel.git
base: cee9395acd8043be0644b25c34bfa86623f2b935
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/f7d70247-4c01-4de9-bc8c-1c0ada6de448/config
./include/trace/events/landlock.h:946:13: error: incompatible pointer types assigning to 'struct pid *' from 'struct pid *const volatile *' [-Wincompatible-pointer-types]
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[alexander@mihalicyn.com brauner@kernel.org davem@davemloft.net edumazet@google.com horms@kernel.org jack@suse.cz kuba@kernel.org kuniyu@google.com linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org netdev@vger.kernel.org oleg@redhat.com pabeni@redhat.com viro@zeniv.linux.org.uk willemb@google.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-08-31 13:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-31 13:22 [moderation/CI] Re: net: support thread-specific pidfds for send and connect syzbot ci
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox