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

1 view
Skip to first unread message

syzbot

unread,
Mar 6, 2024, 6:01:21 PMMar 6
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 5847c9777c30 Merge tag 'cgroup-for-6.8-rc7-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1278f55a180000
kernel config: https://syzkaller.appspot.com/x/.config?x=f10ff55d327ef698
dashboard link: https://syzkaller.appspot.com/bug?extid=875381b0fdbe00c3521f
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/dd0614fb3cf5/disk-5847c977.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5ad60f840a9c/vmlinux-5847c977.xz
kernel image: https://storage.googleapis.com/syzbot-assets/190accdc7b0a/bzImage-5847c977.xz

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

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

read-write to 0xffff88813fc23124 of 4 bytes by task 30961 on cpu 0:
pipe_release+0x6d/0x1c0 fs/pipe.c:739
__fput+0x299/0x630 fs/file_table.c:376
__fput_sync+0x44/0x50 fs/file_table.c:461
__do_sys_close fs/open.c:1554 [inline]
__se_sys_close+0xfa/0x1a0 fs/open.c:1539
__x64_sys_close+0x1f/0x30 fs/open.c:1539
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+0x63/0x6b

read to 0xffff88813fc23124 of 4 bytes by task 293 on cpu 1:
pipe_poll+0x220/0x250 fs/pipe.c:710
vfs_poll include/linux/poll.h:88 [inline]
aio_poll_complete_work+0xd6/0x360 fs/aio.c:1734
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x5b8/0xa40 kernel/workqueue.c:2706
worker_thread+0x525/0x730 kernel/workqueue.c:2787
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:243

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 293 Comm: kworker/1:2 Not tainted 6.8.0-rc7-syzkaller-00020-g5847c9777c30 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: events aio_poll_complete_work
==================================================================


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

unread,
Apr 10, 2024, 7:01:17 PMApr 10
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages