From: syzbot <syzbot+de8b27abd23eac60e15f@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: [syzbot] [fs?] KCSAN: data-race in __lookup_mnt / __se_sys_pivot_root (6)
Date: Wed, 19 Mar 2025 20:28:27 -0700 [thread overview]
Message-ID: <67db8b5b.050a0220.31a16b.0001.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a7f2e10ecd8f Merge tag 'hwmon-fixes-for-v6.14-rc8/6.14' of..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=166a383f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=f33d372c4021745
dashboard link: https://syzkaller.appspot.com/bug?extid=de8b27abd23eac60e15f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/614aabc71b48/disk-a7f2e10e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d47dd90a010a/vmlinux-a7f2e10e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/418d8cf8782b/bzImage-a7f2e10e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+de8b27abd23eac60e15f@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in __lookup_mnt / __se_sys_pivot_root
write to 0xffff888118782d98 of 8 bytes by task 20163 on cpu 0:
unhash_mnt fs/namespace.c:1030 [inline]
__do_sys_pivot_root fs/namespace.c:4456 [inline]
__se_sys_pivot_root+0x850/0x1090 fs/namespace.c:4388
__x64_sys_pivot_root+0x31/0x40 fs/namespace.c:4388
x64_sys_call+0x1abf/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:156
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
read to 0xffff888118782d98 of 8 bytes by task 20164 on cpu 1:
__lookup_mnt+0xa0/0xf0 fs/namespace.c:839
__follow_mount_rcu fs/namei.c:1592 [inline]
handle_mounts fs/namei.c:1622 [inline]
step_into+0x426/0x820 fs/namei.c:1952
walk_component fs/namei.c:2120 [inline]
link_path_walk+0x50e/0x830 fs/namei.c:2479
path_lookupat+0x72/0x2b0 fs/namei.c:2635
filename_lookup+0x150/0x340 fs/namei.c:2665
user_path_at+0x3c/0x120 fs/namei.c:3072
__do_sys_pivot_root fs/namespace.c:4404 [inline]
__se_sys_pivot_root+0x10e/0x1090 fs/namespace.c:4388
__x64_sys_pivot_root+0x31/0x40 fs/namespace.c:4388
x64_sys_call+0x1abf/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:156
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
value changed: 0xffff888106a31d80 -> 0xffff8881004dccc0
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 20164 Comm: syz.0.5594 Tainted: G W 6.14.0-rc7-syzkaller-00074-ga7f2e10ecd8f #0
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
==================================================================
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
next reply other threads:[~2025-03-20 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 3:28 syzbot [this message]
2025-03-20 8:43 ` [syzbot] [fs?] KCSAN: data-race in __lookup_mnt / __se_sys_pivot_root (6) Christian Brauner
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=67db8b5b.050a0220.31a16b.0001.GAE@google.com \
--to=syzbot+de8b27abd23eac60e15f@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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