From: syzbot <syzbot+900324b91168c395f1a2@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: [syzbot] KCSAN: data-race in ext4_mark_iloc_dirty / ext4_mark_iloc_dirty
Date: Mon, 25 Oct 2021 03:57:27 -0700 [thread overview]
Message-ID: <00000000000003d49d05cf2b3a9e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 9c0c4d24ac00 Merge tag 'block-5.15-2021-10-22' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15418e52b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6339b6ea86d89fd7
dashboard link: https://syzkaller.appspot.com/bug?extid=900324b91168c395f1a2
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
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+900324b91168c395f1a2@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in ext4_mark_iloc_dirty / ext4_mark_iloc_dirty
write to 0xffff888104bdf5c8 of 4 bytes by task 505 on cpu 0:
ext4_update_inode_fsync_trans fs/ext4/ext4_jbd2.h:445 [inline]
ext4_do_update_inode fs/ext4/inode.c:5114 [inline]
ext4_mark_iloc_dirty+0x156a/0x1700 fs/ext4/inode.c:5683
ext4_orphan_del+0x593/0x730 fs/ext4/orphan.c:297
ext4_evict_inode+0xb1e/0xdb0 fs/ext4/inode.c:318
evict+0x1c8/0x3c0 fs/inode.c:588
iput_final fs/inode.c:1664 [inline]
iput+0x430/0x580 fs/inode.c:1690
do_unlinkat+0x2d4/0x540 fs/namei.c:4176
__do_sys_unlink fs/namei.c:4217 [inline]
__se_sys_unlink fs/namei.c:4215 [inline]
__x64_sys_unlink+0x2c/0x30 fs/namei.c:4215
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
write to 0xffff888104bdf5c8 of 4 bytes by task 6959 on cpu 1:
ext4_update_inode_fsync_trans fs/ext4/ext4_jbd2.h:445 [inline]
ext4_do_update_inode fs/ext4/inode.c:5114 [inline]
ext4_mark_iloc_dirty+0x156a/0x1700 fs/ext4/inode.c:5683
__ext4_mark_inode_dirty+0x4ec/0x5c0 fs/ext4/inode.c:5879
ext4_evict_inode+0x95e/0xdb0 fs/ext4/inode.c:280
evict+0x1c8/0x3c0 fs/inode.c:588
iput_final fs/inode.c:1664 [inline]
iput+0x430/0x580 fs/inode.c:1690
dentry_unlink_inode+0x273/0x290 fs/dcache.c:376
d_delete+0x78/0xe0 fs/dcache.c:2505
vfs_rmdir+0x2e6/0x300 fs/namei.c:3984
do_rmdir+0x18d/0x330 fs/namei.c:4032
__do_sys_rmdir fs/namei.c:4051 [inline]
__se_sys_rmdir fs/namei.c:4049 [inline]
__x64_sys_rmdir+0x2c/0x30 fs/namei.c:4049
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: 0x0000c326 -> 0x0000c327
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 6959 Comm: syz-executor.2 Tainted: G W 5.15.0-rc6-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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2021-10-25 10:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000003d49d05cf2b3a9e@google.com \
--to=syzbot+900324b91168c395f1a2@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.