Hello,
syzbot found the following issue on:
HEAD commit: 009c9aa5 Linux 5.13-rc6
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=10d03448300000
kernel config:
https://syzkaller.appspot.com/x/.config?x=8b2d74341df68ad2
dashboard link:
https://syzkaller.appspot.com/bug?extid=b3b73ea5ad980e8335b5
compiler: Debian clang version 11.0.1-2
CC: [
amir...@gmail.com ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+b3b73e...@syzkaller.appspotmail.com
loop4: detected capacity change from 0 to 4
EXT4-fs (loop4): Invalid log block size: 192
==================================================================
BUG: KCSAN: data-race in inotify_handle_inode_event / inotify_remove_from_idr
write to 0xffff888100395b38 of 4 bytes by task 30395 on cpu 1:
inotify_remove_from_idr+0x153/0x360 fs/notify/inotify/inotify_user.c:483
inotify_ignored_and_remove_idr+0x30/0x60 fs/notify/inotify/inotify_user.c:504
inotify_freeing_mark+0x19/0x20 fs/notify/inotify/inotify_fsnotify.c:133
fsnotify_free_mark+0xcb/0xf0 fs/notify/mark.c:425
fsnotify_destroy_mark+0x32/0x40 fs/notify/mark.c:434
__do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:791 [inline]
__se_sys_inotify_rm_watch+0x11e/0x1a0 fs/notify/inotify/inotify_user.c:768
__x64_sys_inotify_rm_watch+0x2d/0x40 fs/notify/inotify/inotify_user.c:768
do_syscall_64+0x4a/0x90 arch/x86/entry/common.c:47
entry_SYSCALL_64_after_hwframe+0x44/0xae
read to 0xffff888100395b38 of 4 bytes by task 4859 on cpu 0:
inotify_handle_inode_event+0x194/0x2d0 fs/notify/inotify/inotify_fsnotify.c:113
fsnotify_handle_inode_event fs/notify/fsnotify.c:263 [inline]
fsnotify_handle_event fs/notify/fsnotify.c:310 [inline]
send_to_group fs/notify/fsnotify.c:364 [inline]
fsnotify+0x1040/0x1190 fs/notify/fsnotify.c:541
__fsnotify_parent+0x2f3/0x430 fs/notify/fsnotify.c:232
fsnotify_parent include/linux/fsnotify.h:68 [inline]
fsnotify_file include/linux/fsnotify.h:90 [inline]
fsnotify_close include/linux/fsnotify.h:279 [inline]
__fput+0x1a9/0x4e0 fs/file_table.c:266
____fput+0x11/0x20 fs/file_table.c:313
task_work_run+0xae/0x130 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop kernel/entry/common.c:175 [inline]
exit_to_user_mode_prepare+0x156/0x190 kernel/entry/common.c:209
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x20/0x40 kernel/entry/common.c:302
do_syscall_64+0x56/0x90 arch/x86/entry/common.c:57
entry_SYSCALL_64_after_hwframe+0x44/0xae
value changed: 0x000083c5 -> 0xffffffff
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 4859 Comm: syz-executor.4 Not tainted 5.13.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================
loop4: detected capacity change from 0 to 4
EXT4-fs (loop4): Invalid log block size: 192
---
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.