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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e851dfae4371 Merge tag 'kgdb-5.16-rc1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15bbf31eb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c26351b9e72587a
dashboard link: https://syzkaller.appspot.com/bug?extid=4aa092eb55a73e7ca545
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+4aa092...@syzkaller.appspotmail.com

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

write to 0xffff888104b346a4 of 4 bytes by task 16294 on cpu 1:
jbd2_journal_dirty_metadata+0x2f6/0x690 fs/jbd2/transaction.c:1538
__ext4_handle_dirty_metadata+0xfb/0x5a0 fs/ext4/ext4_jbd2.c:348
ext4_do_update_inode fs/ext4/inode.c:5095 [inline]
ext4_mark_iloc_dirty+0x12d1/0x16e0 fs/ext4/inode.c:5683
ext4_orphan_add+0x82e/0xa40 fs/ext4/orphan.c:168
__ext4_unlink+0x309/0x4e0 fs/ext4/namei.c:3195
ext4_unlink+0x1ea/0x3b0 fs/ext4/namei.c:3231
vfs_unlink+0x257/0x450 fs/namei.c:4100
do_unlinkat+0x278/0x540 fs/namei.c:4167
__do_sys_unlink fs/namei.c:4215 [inline]
__se_sys_unlink fs/namei.c:4213 [inline]
__x64_sys_unlink+0x2c/0x30 fs/namei.c:4213
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888104b346a4 of 4 bytes by task 32528 on cpu 0:
jbd2_journal_dirty_metadata+0x16f/0x690 fs/jbd2/transaction.c:1506
__ext4_handle_dirty_metadata+0xfb/0x5a0 fs/ext4/ext4_jbd2.c:348
ext4_do_update_inode fs/ext4/inode.c:5095 [inline]
ext4_mark_iloc_dirty+0x12d1/0x16e0 fs/ext4/inode.c:5683
ext4_xattr_set_handle+0xf77/0x1120 fs/ext4/xattr.c:2402
ext4_initxattrs+0x66/0xb0 fs/ext4/xattr_security.c:44
security_inode_init_security+0x1a9/0x260 security/security.c:1100
ext4_init_security+0x30/0x40 fs/ext4/xattr_security.c:58
__ext4_new_inode+0x29a3/0x2fc0 fs/ext4/ialloc.c:1325
ext4_symlink+0x2cc/0x700 fs/ext4/namei.c:3293
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/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x00000000 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 32528 Comm: syz-executor.3 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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.