From: syzbot <syzbot+702361cf7e3d95758761@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hughd@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [mm?] KCSAN: data-race in generic_fillattr / shmem_mknod (2)
Date: Mon, 24 Apr 2023 00:58:48 -0700 [thread overview]
Message-ID: <0000000000007337c705fa1060e2@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 457391b03803 Linux 6.3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13226cf0280000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c81c9a3d360ebcf
dashboard link: https://syzkaller.appspot.com/bug?extid=702361cf7e3d95758761
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6438dcb1c42d/disk-457391b0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/20596c249e47/vmlinux-457391b0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb715366a3e5/bzImage-457391b0.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+702361cf7e3d95758761@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in generic_fillattr / shmem_mknod
read-write to 0xffff8881049a9408 of 8 bytes by task 3383 on cpu 0:
shmem_mknod+0xdd/0x180 mm/shmem.c:2942
shmem_create+0x34/0x40 mm/shmem.c:2994
lookup_open fs/namei.c:3416 [inline]
open_last_lookups fs/namei.c:3484 [inline]
path_openat+0xd96/0x1d00 fs/namei.c:3712
do_filp_open+0xf6/0x200 fs/namei.c:3742
do_sys_openat2+0xb5/0x2a0 fs/open.c:1348
do_sys_open fs/open.c:1364 [inline]
__do_sys_openat fs/open.c:1380 [inline]
__se_sys_openat fs/open.c:1375 [inline]
__x64_sys_openat+0xf3/0x120 fs/open.c:1375
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
read to 0xffff8881049a9408 of 8 bytes by task 4291 on cpu 1:
i_size_read include/linux/fs.h:866 [inline]
generic_fillattr+0x13f/0x1e0 fs/stat.c:58
shmem_getattr+0x32a/0x3b0 mm/shmem.c:1068
vfs_getattr_nosec+0x1e3/0x3c0 fs/stat.c:133
vfs_getattr fs/stat.c:170 [inline]
vfs_statx+0x156/0x300 fs/stat.c:242
vfs_fstatat fs/stat.c:276 [inline]
__do_sys_newfstatat fs/stat.c:446 [inline]
__se_sys_newfstatat+0x8a/0x2a0 fs/stat.c:440
__x64_sys_newfstatat+0x55/0x60 fs/stat.c:440
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
value changed: 0x0000000000001644 -> 0x0000000000001658
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 4291 Comm: udevd Not tainted 6.3.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
==================================================================
---
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.
next reply other threads:[~2023-04-24 7:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 7:58 syzbot [this message]
2023-04-24 8:26 ` [syzbot] [mm?] KCSAN: data-race in generic_fillattr / shmem_mknod (2) 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
-- strict thread matches above, loose matches on Subject: below --
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=0000000000007337c705fa1060e2@google.com \
--to=syzbot+702361cf7e3d95758761@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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