KCSAN: data-race in ext4_mark_iloc_dirty / find_inode_bit.isra.0

4 views
Skip to first unread message

syzbot

unread,
Jan 8, 2020, 12:04:10 AM1/8/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 245a4300 Merge branch 'rcu/kcsan' into tip/locking/kcsan
git tree: https://github.com/google/ktsan.git kcsan
console output: https://syzkaller.appspot.com/x/log.txt?x=1137d076e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4b9db179318d21f
dashboard link: https://syzkaller.appspot.com/bug?extid=ec8658d17930e493daed
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [adilger...@dilger.ca linux...@vger.kernel.org
linux-...@vger.kernel.org ty...@mit.edu el...@google.com]

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+ec8658...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in ext4_mark_iloc_dirty / find_inode_bit.isra.0

write to 0xffff8881193b8814 of 4 bytes by task 18642 on cpu 0:
ext4_do_update_inode fs/ext4/inode.c:4938 [inline]
ext4_mark_iloc_dirty+0x74a/0x1580 fs/ext4/inode.c:5547
ext4_mark_inode_dirty+0xe9/0x420 fs/ext4/inode.c:5740
ext4_ext_tree_init+0x92/0xb0 fs/ext4/extents.c:872
__ext4_new_inode+0x2d94/0x2f10 fs/ext4/ialloc.c:1164
ext4_symlink+0x31c/0x9b0 fs/ext4/namei.c:3275
vfs_symlink fs/namei.c:4131 [inline]
vfs_symlink+0x218/0x310 fs/namei.c:4117
do_symlinkat+0x1a5/0x1e0 fs/namei.c:4158
__do_sys_symlink fs/namei.c:4177 [inline]
__se_sys_symlink fs/namei.c:4175 [inline]
__x64_sys_symlink+0x3f/0x50 fs/namei.c:4175
do_syscall_64+0xcc/0x3a0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x44/0xa9

read to 0xffff8881193b8814 of 4 bytes by task 18643 on cpu 1:
recently_deleted fs/ext4/ialloc.c:693 [inline]
find_inode_bit.isra.0+0x1d8/0x300 fs/ext4/ialloc.c:717
__ext4_new_inode+0xd45/0x2f10 fs/ext4/ialloc.c:909
ext4_symlink+0x31c/0x9b0 fs/ext4/namei.c:3275
vfs_symlink fs/namei.c:4131 [inline]
vfs_symlink+0x218/0x310 fs/namei.c:4117
do_symlinkat+0x1a5/0x1e0 fs/namei.c:4158
__do_sys_symlink fs/namei.c:4177 [inline]
__se_sys_symlink fs/namei.c:4175 [inline]
__x64_sys_symlink+0x3f/0x50 fs/namei.c:4175
do_syscall_64+0xcc/0x3a0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x44/0xa9

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 18643 Comm: syz-executor.4 Not tainted 5.5.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
==================================================================


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Jul 23, 2020, 8:44:16 AM7/23/20
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages