[moderation] [kernfs?] KCSAN: data-race in __kernfs_remove / cleanup_glue_dir (9)

1 view
Skip to first unread message

syzbot

unread,
May 31, 2024, 5:54:21 PMMay 31
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d8ec19857b09 Merge tag 'net-6.10-rc2' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15b69bd2980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b639694183430f97
dashboard link: https://syzkaller.appspot.com/bug?extid=5093995590c9b888c585
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org t...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4c525cb10506/disk-d8ec1985.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5d3c75ffceb2/vmlinux-d8ec1985.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5a992c1884ee/bzImage-d8ec1985.xz

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

==================================================================
BUG: KCSAN: data-race in __kernfs_remove / cleanup_glue_dir

read-write to 0xffff888117392c78 of 8 bytes by task 4802 on cpu 1:
kernfs_unlink_sibling fs/kernfs/dir.c:415 [inline]
__kernfs_remove+0x2ff/0x480 fs/kernfs/dir.c:1492
kernfs_remove+0x4e/0x70 fs/kernfs/dir.c:1528
sysfs_remove_dir+0x7e/0xa0 fs/sysfs/dir.c:101
__kobject_del+0x9d/0x1a0 lib/kobject.c:604
kobject_del+0x2e/0x50 lib/kobject.c:627
device_del+0x70f/0x780 drivers/base/core.c:3930
device_unregister+0x15/0x40 drivers/base/core.c:3951
wakeup_source_sysfs_remove+0x25/0x30 drivers/base/power/wakeup_stats.c:208
wakeup_source_unregister+0xee/0x110 drivers/base/power/wakeup.c:244
__ep_remov


---
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