syzbot


KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event

Status: auto-closed as invalid on 2022/09/07 06:46
Subsystems: fs
[Documentation on labels]
First crash: 632d, last: 632d
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 1 17d 17d 0/26 moderation: reported on 2024/04/09 13:13
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (4) fs 1 278d 278d 0/26 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 537d 537d 0/26 auto-obsoleted due to no activity on 2022/12/10 20:40
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (3) fs 1 385d 385d 0/26 auto-obsoleted due to no activity on 2023/05/12 13:04
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (5) fs 3 178d 189d 0/26 auto-obsoleted due to no activity on 2023/12/04 18:59

Sample crash report:
loop3: detected capacity change from 0 to 264192
EXT4-fs (loop3): Invalid log block size: 10487040
==================================================================
BUG: KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event

write to 0xffff8881039a8ea4 of 4 bytes by task 29545 on cpu 1:
 fsnotify_free_mark fs/notify/mark.c:481 [inline]
 fsnotify_destroy_mark+0x172/0x1c0 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+0x2d/0x40 fs/notify/inotify/inotify_user.c:794
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

read to 0xffff8881039a8ea4 of 4 bytes by task 19892 on cpu 0:
 inotify_handle_inode_event+0x299/0x2e0 fs/notify/inotify/inotify_fsnotify.c:125
 fsnotify_handle_inode_event fs/notify/fsnotify.c:264 [inline]
 fsnotify_handle_event fs/notify/fsnotify.c:316 [inline]
 send_to_group fs/notify/fsnotify.c:364 [inline]
 fsnotify+0x138e/0x1550 fs/notify/fsnotify.c:570
 __fsnotify_parent+0x30b/0x470 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+0x1d7/0x510 fs/file_table.c:303
 ____fput+0x11/0x20 fs/file_table.c:350
 task_work_run+0x8e/0x110 kernel/task_work.c:177
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0x124/0x130 kernel/entry/common.c:169
 exit_to_user_mode_prepare kernel/entry/common.c:201 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
 syscall_exit_to_user_mode+0x6a/0x90 kernel/entry/common.c:294
 do_syscall_64+0x37/0x70 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: 19892 Comm: syz-executor.3 Not tainted 5.19.0-syzkaller-01583-g7d0d3fa7339e-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/08/03 06:43 upstream 7d0d3fa7339e 1c9013ac .config console log report info ci2-upstream-kcsan-gce KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event
* Struck through repros no longer work on HEAD.