KCSAN: data-race in jbd2_journal_stop / jbd2_journal_stop (2)

4 views
Skip to first unread message

syzbot

unread,
Nov 12, 2021, 6:52:23 PM11/12/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 5833291ab6de Merge tag 'pci-v5.16-fixes-1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12f37de1b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=bda4b60fed516f35
dashboard link: https://syzkaller.appspot.com/bug?extid=49e18dade46e9a02e8a8
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [ja...@suse.com linux...@vger.kernel.org linux-...@vger.kernel.org ty...@mit.edu]

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+49e18d...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in jbd2_journal_stop / jbd2_journal_stop

write to 0xffff88810303fcf8 of 4 bytes by task 1825 on cpu 0:
jbd2_journal_stop+0x2e6/0x6a0 fs/jbd2/transaction.c:1874
__ext4_journal_stop+0x99/0x110 fs/ext4/ext4_jbd2.c:127
ext4_evict_inode+0xc13/0xf10 fs/ext4/inode.c:333
evict+0x1aa/0x410 fs/inode.c:592
iput_final fs/inode.c:1672 [inline]
iput+0x3ef/0x580 fs/inode.c:1698
dentry_unlink_inode+0x23d/0x250 fs/dcache.c:376
d_delete+0x78/0xa0 fs/dcache.c:2505
vfs_rmdir+0x2bf/0x2e0 fs/namei.c:3982
do_rmdir+0x18d/0x330 fs/namei.c:4030
__do_sys_rmdir fs/namei.c:4049 [inline]
__se_sys_rmdir fs/namei.c:4047 [inline]
__x64_sys_rmdir+0x2c/0x30 fs/namei.c:4047
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff88810303fcf8 of 4 bytes by task 25626 on cpu 1:
jbd2_journal_stop+0x297/0x6a0 fs/jbd2/transaction.c:1870
__ext4_journal_stop+0x99/0x110 fs/ext4/ext4_jbd2.c:127
ext4_symlink+0x4db/0x700 fs/ext4/namei.c:3365
vfs_symlink+0x241/0x330 fs/namei.c:4248
do_symlinkat+0x104/0x380 fs/namei.c:4277
__do_sys_symlink fs/namei.c:4299 [inline]
__se_sys_symlink fs/namei.c:4297 [inline]
__x64_sys_symlink+0x52/0x60 fs/namei.c:4297
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x0000641c -> 0x00000721

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


---
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.

syzbot

unread,
Jan 25, 2022, 4:02:22 AM1/25/22
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