syzbot


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

Status: auto-obsoleted due to no activity on 2024/04/02 20:17
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+6b63a49c4822f9638fcb@syzkaller.appspotmail.com
First crash: 66d, last: 47d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event (4) fs 1 137d 125d 0/26 auto-obsoleted due to no activity on 2024/01/03 04:57
upstream KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event fs 1 280d 280d 0/26 auto-obsoleted due to no activity on 2023/08/13 07:22
upstream KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event (3) fs 2 196d 198d 0/26 auto-obsoleted due to no activity on 2023/11/05 21:43
upstream KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event (2) fs 1 238d 238d 0/26 auto-obsoleted due to no activity on 2023/09/24 11:29

Sample crash report:
loop4: detected capacity change from 0 to 512
EXT4-fs (loop4): Invalid log block size: 68
==================================================================
BUG: KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event

write to 0xffff888103aa75e4 of 4 bytes by task 3432 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:816 [inline]
 __se_sys_inotify_rm_watch+0xfd/0x180 fs/notify/inotify/inotify_user.c:793
 __x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:793
 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 0xffff888103aa75e4 of 4 bytes by task 21054 on cpu 0:
 fsnotify_handle_inode_event+0xfa/0x200 fs/notify/fsnotify.c:256
 fsnotify_handle_event fs/notify/fsnotify.c:316 [inline]
 send_to_group fs/notify/fsnotify.c:364 [inline]
 fsnotify+0x101d/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:100 [inline]
 fsnotify_close include/linux/fsnotify.h:381 [inline]
 __fput+0x1da/0x630 fs/file_table.c:362
 __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

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 21054 Comm: syz-executor.4 Not tainted 6.8.0-rc6-syzkaller-00011-g45ec2f5f6ed3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
==================================================================

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/27 20:17 upstream 45ec2f5f6ed3 d367cbe5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event
2024/02/08 22:16 upstream 047371968ffc 7f07e9b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event
* Struck through repros no longer work on HEAD.