From: syzbot <syzbot+702361cf7e3d95758761@syzkaller.appspotmail.com>
To: aha310510@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] KCSAN: data-race in generic_fillattr / shmem_mknod (2)
Date: Sat, 07 Sep 2024 23:49:01 -0700 [thread overview]
Message-ID: <00000000000016108b0621960915@google.com> (raw)
In-Reply-To: <20240908060931.7380-1-aha310510@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KCSAN: data-race in ext4_fill_raw_inode / ext4_orphan_del
==================================================================
BUG: KCSAN: data-race in ext4_fill_raw_inode / ext4_orphan_del
write to 0xffff8881054ccdd4 of 4 bytes by task 3372 on cpu 1:
ext4_orphan_del+0x54d/0x6e0 fs/ext4/orphan.c:296
ext4_evict_inode+0xac3/0xdc0 fs/ext4/inode.c:289
evict+0x2d7/0x560 fs/inode.c:704
iput_final fs/inode.c:1838 [inline]
iput+0x432/0x5c0 fs/inode.c:1864
d_delete_notify include/linux/fsnotify.h:332 [inline]
vfs_rmdir+0x29f/0x320 fs/namei.c:4306
do_rmdir+0x194/0x320 fs/namei.c:4352
__do_sys_unlinkat fs/namei.c:4528 [inline]
__se_sys_unlinkat fs/namei.c:4522 [inline]
__x64_sys_unlinkat+0xa2/0xb0 fs/namei.c:4522
x64_sys_call+0x25fd/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:264
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x54/0x120 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x76/0x7e
read to 0xffff8881054ccdd4 of 4 bytes by task 3392 on cpu 0:
ext4_fill_raw_inode+0x64b/0xe80 fs/ext4/inode.c:4348
ext4_do_update_inode fs/ext4/inode.c:5151 [inline]
ext4_mark_iloc_dirty+0x2e9/0xe10 fs/ext4/inode.c:5781
__ext4_mark_inode_dirty+0x314/0x440 fs/ext4/inode.c:5985
__ext4_ext_dirty fs/ext4/extents.c:202 [inline]
ext4_ext_remove_space+0x28ca/0x2c80 fs/ext4/extents.c:3038
ext4_ext_truncate+0xc4/0x150 fs/ext4/extents.c:4441
ext4_truncate+0x773/0xb10 fs/ext4/inode.c:4218
ext4_evict_inode+0x8b4/0xdc0 fs/ext4/inode.c:258
evict+0x2d7/0x560 fs/inode.c:704
iput_final fs/inode.c:1838 [inline]
iput+0x432/0x5c0 fs/inode.c:1864
d_delete_notify include/linux/fsnotify.h:332 [inline]
vfs_rmdir+0x29f/0x320 fs/namei.c:4306
do_rmdir+0x194/0x320 fs/namei.c:4352
__do_sys_unlinkat fs/namei.c:4528 [inline]
__se_sys_unlinkat fs/namei.c:4522 [inline]
__x64_sys_unlinkat+0xa2/0xb0 fs/namei.c:4522
x64_sys_call+0x25fd/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:264
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x54/0x120 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x76/0x7e
value changed: 0x0000079a -> 0x0000078b
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 3392 Comm: syz-executor.1 Not tainted 6.11.0-rc6-syzkaller-00326-gd1f2d51b711a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
==================================================================
Tested on:
commit: d1f2d51b Merge tag 'clk-fixes-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=151e1ffb980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e81d40b0108ea8fe
dashboard link: https://syzkaller.appspot.com/bug?extid=702361cf7e3d95758761
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next prev parent reply other threads:[~2024-09-08 6:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 6:09 KCSAN: data-race in generic_fillattr / shmem_mknod (2) Jeongjun Park
2024-09-08 6:49 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-08 11:33 [syzbot] [mm?] " Jeongjun Park
2024-09-08 12:08 ` syzbot
2024-09-08 11:33 Jeongjun Park
2024-09-08 11:49 ` syzbot
2024-09-08 10:27 Jeongjun Park
2024-09-08 10:44 ` [syzbot] [mm?] " syzbot
2024-09-08 8:34 Jeongjun Park
2024-09-08 9:45 ` [syzbot] [mm?] " syzbot
2024-09-08 8:16 Jeongjun Park
2024-09-08 9:31 ` [syzbot] [mm?] " syzbot
2024-09-08 7:47 Jeongjun Park
2024-09-08 8:01 ` [syzbot] [mm?] " syzbot
2024-09-08 6:27 Jeongjun Park
2024-09-08 6:59 ` [syzbot] [mm?] " syzbot
2024-09-08 5:23 Jeongjun Park
2024-09-08 5:39 ` [syzbot] [mm?] " syzbot
2023-04-24 7:58 syzbot
2023-04-24 8:26 ` Dmitry Vyukov
2023-05-01 5:15 ` Tetsuo Handa
2023-05-01 14:05 ` Tetsuo Handa
2023-05-02 10:13 ` Tetsuo Handa
2023-05-02 6:13 ` Dmitry Vyukov
2024-01-12 12:15 ` syzbot
2024-09-18 4:03 ` Jeongjun Park
2024-09-18 4:58 ` syzbot
2024-09-18 6:26 ` Jeongjun Park
2024-09-18 6:31 ` syzbot
2024-09-18 6:41 ` Jeongjun Park
2024-09-18 7:37 ` syzbot
2024-09-18 7:46 ` Jeongjun Park
2024-09-18 7:58 ` syzbot
2024-09-20 14:27 ` Jeongjun Park
2024-09-20 14:32 ` syzbot
2024-09-20 14:33 ` Jeongjun Park
2024-09-20 14:43 ` syzbot
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=00000000000016108b0621960915@google.com \
--to=syzbot+702361cf7e3d95758761@syzkaller.appspotmail.com \
--cc=aha310510@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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.