syzbot


KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (3)

Status: auto-obsoleted due to no activity on 2023/05/12 13:04
Subsystems: fs
[Documentation on labels]
First crash: 434d, last: 434d
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (6) fs 2 32d 66d 0/27 moderation: reported on 2024/04/09 13:13
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event fs 1 681d 681d 0/27 auto-closed as invalid on 2022/09/07 06:46
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (4) fs 1 327d 327d 0/27 auto-obsoleted due to no activity on 2023/08/27 10:05
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (2) fs 1 586d 586d 0/27 auto-obsoleted due to no activity on 2022/12/10 20:40
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (5) fs 3 227d 238d 0/27 auto-obsoleted due to no activity on 2023/12/04 18:59

Sample crash report:
EXT4-fs error (device loop2): ext4_ext_check_inode:520: inode #2: comm syz-executor.2: pblk 0 bad header/extent: invalid eh_max - magic f30a, entries 1, max 0(0), depth 0(0)
EXT4-fs (loop2): get root inode failed
EXT4-fs (loop2): mount failed
==================================================================
BUG: KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event

write to 0xffff888104cba684 of 4 bytes by task 17819 on cpu 1:
 fsnotify_free_mark fs/notify/mark.c:481 [inline]
 fsnotify_destroy_mark+0x146/0x190 fs/notify/mark.c:499
 __do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:817 [inline]
 __se_sys_inotify_rm_watch+0xf7/0x170 fs/notify/inotify/inotify_user.c:794
 __x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:794
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

read to 0xffff888104cba684 of 4 bytes by task 425 on cpu 0:
 inotify_handle_inode_event+0x280/0x2c0 fs/notify/inotify/inotify_fsnotify.c:125
 fsnotify_handle_inode_event+0x19b/0x1f0 fs/notify/fsnotify.c:264
 fsnotify_handle_event fs/notify/fsnotify.c:316 [inline]
 send_to_group fs/notify/fsnotify.c:364 [inline]
 fsnotify+0x101c/0x1150 fs/notify/fsnotify.c:570
 __fsnotify_parent+0x307/0x480 fs/notify/fsnotify.c:230
 fsnotify_parent include/linux/fsnotify.h:77 [inline]
 fsnotify_file include/linux/fsnotify.h:99 [inline]
 fsnotify_close include/linux/fsnotify.h:341 [inline]
 __fput+0x4b0/0x570 fs/file_table.c:307
 ____fput+0x15/0x20 fs/file_table.c:349
 task_work_run+0x123/0x160 kernel/task_work.c:179
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0xd1/0xe0 kernel/entry/common.c:171
 exit_to_user_mode_prepare+0x6c/0xb0 kernel/entry/common.c:204
 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
 syscall_exit_to_user_mode+0x26/0x140 kernel/entry/common.c:297
 do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 425 Comm: syz-executor.2 Not tainted 6.3.0-rc5-syzkaller-00137-gf2afccfefe7b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/07 13:03 upstream f2afccfefe7b f7ba566d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event
* Struck through repros no longer work on HEAD.