syzbot


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

Status: auto-obsoleted due to no activity on 2023/12/04 18:59
Subsystems: fs
[Documentation on labels]
First crash: 238d, last: 227d
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 (3) fs 1 434d 434d 0/27 auto-obsoleted due to no activity on 2023/05/12 13:04

Sample crash report:
loop3: detected capacity change from 0 to 512
EXT4-fs (loop3): inodes count not valid: 26 vs 32
==================================================================
BUG: KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event

write to 0xffff888103ba2e04 of 4 bytes by task 3192 on cpu 0:
 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+0xfd/0x180 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 0xffff888103ba2e04 of 4 bytes by task 12140 on cpu 1:
 inotify_handle_inode_event+0x2c5/0x310 fs/notify/inotify/inotify_fsnotify.c:132
 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:101 [inline]
 fsnotify_close include/linux/fsnotify.h:343 [inline]
 __fput+0x249/0x5f0 fs/file_table.c:370
 __fput_sync+0x44/0x50 fs/file_table.c:465
 __do_sys_close fs/open.c:1572 [inline]
 __se_sys_close+0xfa/0x1a0 fs/open.c:1557
 __x64_sys_close+0x1f/0x30 fs/open.c:1557
 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

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 12140 Comm: syz-executor.3 Not tainted 6.6.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
==================================================================

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/10/30 18:53 upstream ffc253263a13 b5729d82 .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
2023/10/27 16:04 upstream 750b95887e56 3c418d72 .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
2023/10/20 08:31 upstream ce55c22ec8b2 a42250d2 .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.