[moderation] [fs?] upstream test error: KCSAN: data-race in pollwake / pollwake (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3e5e6c9900c3 Merge tag 'nfsd-6.12-3' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13f21aa7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd88d664711c92e2
dashboard link: https://syzkaller.appspot.com/bug?extid=51ab8c9ec6aa929e3344
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5799eba5015c/disk-3e5e6c99.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ca21797441cb/vmlinux-3e5e6c99.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7529958cf49b/bzImage-3e5e6c99.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+51ab8c...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in pollwake / pollwake

write to 0xffffc9000132fa00 of 4 bytes by task 3326 on cpu 0:
__pollwake fs/select.c:195 [inline]
pollwake+0xbe/0x110 fs/select.c:215
__wake_up_common kernel/sched/wait.c:89 [inline]
__wake_up_common_lock kernel/sched/wait.c:106 [inline]
__wake_up_sync_key+0x51/0x80 kernel/sched/wait.c:173
pipe_write+0x962/0xd20 fs/pipe.c:602
new_sync_write fs/read_write.c:590 [inline]
vfs_write+0x77f/0x920 fs/read_write.c:683
ksys_write+0xeb/0x1b0 fs/read_write.c:736
__do_sys_write fs/read_write.c:748 [inline]
__se_sys_write fs/read_write.c:745 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:745
x64_sys_call+0x27dd/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

write to 0xffffc9000132fa00 of 4 bytes by task 3325 on cpu 1:
__pollwake fs/select.c:195 [inline]
pollwake+0xbe/0x110 fs/select.c:215
__wake_up_common kernel/sched/wait.c:89 [inline]
__wake_up_common_lock kernel/sched/wait.c:106 [inline]
__wake_up_sync_key+0x51/0x80 kernel/sched/wait.c:173
pipe_write+0x962/0xd20 fs/pipe.c:602
new_sync_write fs/read_write.c:590 [inline]
vfs_write+0x77f/0x920 fs/read_write.c:683
ksys_write+0xeb/0x1b0 fs/read_write.c:736
__do_sys_write fs/read_write.c:748 [inline]
__se_sys_write fs/read_write.c:745 [inline]
__x64_sys_write+0x42/0x50 fs/read_write.c:745
x64_sys_call+0x27dd/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000000 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 3325 Comm: syz-executor Not tainted 6.12.0-rc5-syzkaller-00308-g3e5e6c9900c3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.