[moderation] [fs?] KCSAN: data-race in d_delete / step_into (6)

3 views
Skip to first unread message

syzbot

unread,
Dec 7, 2023, 5:03:26 AM12/7/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: bee0e7762ad2 Merge tag 'for-linus-iommufd' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1293847ae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac34c1f29a8029df
dashboard link: https://syzkaller.appspot.com/bug?extid=67b54b5d7a1e21b943ac
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/233be5f65dd2/disk-bee0e776.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/94423738a289/vmlinux-bee0e776.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0b977463fa9a/bzImage-bee0e776.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67b54b...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in d_delete / step_into

read-write to 0xffff88813df27240 of 4 bytes by task 3123 on cpu 0:
d_delete+0x6c/0xf0 fs/dcache.c:2563
d_delete_notify+0x30/0xe0 include/linux/fsnotify.h:260
vfs_unlink+0x305/0x3e0 fs/namei.c:4333
do_unlinkat+0x236/0x4c0 fs/namei.c:4382
__do_sys_unlink fs/namei.c:4430 [inline]
__se_sys_unlink fs/namei.c:4428 [inline]
__x64_sys_unlink+0x30/0x40 fs/namei.c:4428
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff88813df27240 of 4 bytes by task 2779 on cpu 1:
__follow_mount_rcu fs/namei.c:1487 [inline]
handle_mounts fs/namei.c:1538 [inline]
step_into+0xe7/0x800 fs/namei.c:1840
walk_component+0x164/0x230 fs/namei.c:2008
lookup_last fs/namei.c:2459 [inline]
path_lookupat+0x10a/0x2a0 fs/namei.c:2483
filename_lookup+0x126/0x300 fs/namei.c:2512
user_path_at_empty+0x42/0x110 fs/namei.c:2911
do_readlinkat+0x92/0x210 fs/stat.c:494
__do_sys_readlink fs/stat.c:527 [inline]
__se_sys_readlink fs/stat.c:524 [inline]
__x64_sys_readlink+0x47/0x50 fs/stat.c:524
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00600108 -> 0x00000008

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 2779 Comm: udevd Not tainted 6.7.0-rc4-syzkaller-00009-gbee0e7762ad2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/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 syzk...@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
Reply all
Reply to author
Forward
0 new messages