[moderation] [fs?] KCSAN: data-race in pipe_poll / pipe_release (5)

0 views
Skip to first unread message

syzbot

unread,
May 1, 2024, 5:41:25 AMMay 1
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 18daea77cca6 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1710b2a0980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c3beef2aff822313
dashboard link: https://syzkaller.appspot.com/bug?extid=60311aabdd9f5689490e
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]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bf6a505db597/disk-18daea77.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eca1bb0a1073/vmlinux-18daea77.xz
kernel image: https://storage.googleapis.com/syzbot-assets/71723d8f8875/bzImage-18daea77.xz

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

==================================================================
BUG: KCSAN: data-race in pipe_poll / pipe_release

write to 0xffff88817fdf8c68 of 4 bytes by task 17103 on cpu 0:
pipe_release+0xb3/0x1c0 fs/pipe.c:731
__fput+0x2c1/0x660 fs/file_table.c:422
__fput_sync+0x44/0x60 fs/file_table.c:507
__do_sys_close fs/open.c:1556 [inline]
__se_sys_close+0x101/0x1b0 fs/open.c:1541
__x64_sys_close+0x1f/0x30 fs/open.c:1541
x64_sys_call+0x25b9/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:4
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88817fdf8c68 of 4 bytes by task 17108 on cpu 1:
pipe_poll+0x17d/0x260 fs/pipe.c:689
vfs_poll include/linux/poll.h:84 [inline]
io_poll_check_events io_uring/poll.c:303 [inline]
io_poll_task_func+0x151/0x910 io_uring/poll.c:357
io_handle_tw_list+0x114/0x240 io_uring/io_uring.c:1198
tctx_task_work_run+0x6c/0x1b0 io_uring/io_uring.c:1270
tctx_task_work+0x40/0x80 io_uring/io_uring.c:1288
task_work_run+0x13a/0x1a0 kernel/task_work.c:180
get_signal+0xeee/0x1080 kernel/signal.c:2683
arch_do_signal_or_restart+0x95/0x4b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x59/0x130 kernel/entry/common.c:218
do_syscall_64+0xda/0x1d0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 17108 Comm: syz-executor.4 Tainted: G W 6.9.0-rc6-syzkaller-00046-g18daea77cca6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/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
Reply all
Reply to author
Forward
0 new messages