mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Fri, 20 Sep 2024 07:43:03 -0700	[thread overview]
Message-ID: <66ed89f7.050a0220.2abe4d.0017.GAE@google.com> (raw)
In-Reply-To: <20240920143350.4194-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 0xffff8881080b3214 of 4 bytes by task 3410 on cpu 1:
 ext4_orphan_del+0x550/0x6e0 fs/ext4/orphan.c:296
 ext4_evict_inode+0xac3/0xdc0 fs/ext4/inode.c:289
 evict+0x2f0/0x570 fs/inode.c:731
 iput_final fs/inode.c:1883 [inline]
 iput+0x42a/0x5b0 fs/inode.c:1909
 d_delete_notify include/linux/fsnotify.h:332 [inline]
 vfs_rmdir+0x29f/0x320 fs/namei.c:4353
 do_rmdir+0x194/0x320 fs/namei.c:4399
 __do_sys_unlinkat fs/namei.c:4575 [inline]
 __se_sys_unlinkat fs/namei.c:4569 [inline]
 __x64_sys_unlinkat+0xa2/0xb0 fs/namei.c:4569
 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 0xffff8881080b3214 of 4 bytes by task 3404 on cpu 0:
 ext4_fill_raw_inode+0x28d/0xe80 fs/ext4/inode.c:4323
 ext4_do_update_inode fs/ext4/inode.c:5148 [inline]
 ext4_mark_iloc_dirty+0x2e9/0xe00 fs/ext4/inode.c:5778
 __ext4_mark_inode_dirty+0x314/0x440 fs/ext4/inode.c:5982
 __ext4_ext_dirty fs/ext4/extents.c:202 [inline]
 ext4_ext_rm_leaf fs/ext4/extents.c:2722 [inline]
 ext4_ext_remove_space+0x126d/0x2c80 fs/ext4/extents.c:2934
 ext4_ext_truncate+0xc4/0x150 fs/ext4/extents.c:4441
 ext4_truncate+0x776/0xb10 fs/ext4/inode.c:4215
 ext4_evict_inode+0x8b4/0xdc0 fs/ext4/inode.c:258
 evict+0x2f0/0x570 fs/inode.c:731
 iput_final fs/inode.c:1883 [inline]
 iput+0x42a/0x5b0 fs/inode.c:1909
 d_delete_notify include/linux/fsnotify.h:332 [inline]
 vfs_rmdir+0x29f/0x320 fs/namei.c:4353
 do_rmdir+0x194/0x320 fs/namei.c:4399
 __do_sys_unlinkat fs/namei.c:4575 [inline]
 __se_sys_unlinkat fs/namei.c:4569 [inline]
 __x64_sys_unlinkat+0xa2/0xb0 fs/namei.c:4569
 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: 0x0000079c -> 0x0000078b

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 3404 Comm: syz-executor.0 Not tainted 6.11.0-syzkaller-07341-gbaeb9a7d8b60-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
==================================================================


Tested on:

commit:         baeb9a7d Merge tag 'sched-rt-2024-09-17' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1642ae9f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4ca35e71cb9a0a41
dashboard link: https://syzkaller.appspot.com/bug?extid=702361cf7e3d95758761
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=143cae9f980000


  reply	other threads:[~2024-09-20 14:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2024-09-08  5:23 Jeongjun Park
2024-09-08  5:39 ` [syzbot] [mm?] " syzbot
2024-09-08  6:09 Jeongjun Park
2024-09-08  6:49 ` [syzbot] [mm?] " syzbot
2024-09-08  6:27 Jeongjun Park
2024-09-08  6:59 ` [syzbot] [mm?] " syzbot
2024-09-08  7:47 Jeongjun Park
2024-09-08  8:01 ` [syzbot] [mm?] " syzbot
2024-09-08  8:16 Jeongjun Park
2024-09-08  9:31 ` [syzbot] [mm?] " syzbot
2024-09-08  8:34 Jeongjun Park
2024-09-08  9:45 ` [syzbot] [mm?] " syzbot
2024-09-08 10:27 Jeongjun Park
2024-09-08 10:44 ` [syzbot] [mm?] " syzbot
2024-09-08 11:33 Jeongjun Park
2024-09-08 11:49 ` syzbot
2024-09-08 11:33 Jeongjun Park
2024-09-08 12:08 ` 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=66ed89f7.050a0220.2abe4d.0017.GAE@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome