[moderation] [kernel?] KCSAN: data-race in process_one_work / process_one_work

3 views
Skip to first unread message

syzbot

unread,
Dec 7, 2023, 7:00:31 PM12/7/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 25aa0bebba72 Merge tag 'net-6.5-rc6' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1197723da80000
kernel config: https://syzkaller.appspot.com/x/.config?x=a1abf5b066126c86
dashboard link: https://syzkaller.appspot.com/bug?extid=01affb1491750534256d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16def407a80000
CC: [b...@alien8.de bra...@kernel.org dave....@linux.intel.com h...@zytor.com linux-...@vger.kernel.org mi...@redhat.com tg...@linutronix.de x...@kernel.org]

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/37e7726f4b59/disk-25aa0beb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c08aceaec1ed/vmlinux-25aa0beb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/49fb33802692/bzImage-25aa0beb.xz

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

==================================================================
BUG: KCSAN: data-race in process_one_work / process_one_work

read-write to 0xffff888104a443a0 of 8 bytes by task 3108 on cpu 0:
process_one_work+0x45f/0x860 kernel/workqueue.c:2606
worker_thread+0x5f2/0xa10 kernel/workqueue.c:2751
kthread+0x1d7/0x210 kernel/kthread.c:389
ret_from_fork+0x2e/0x40 arch/x86/kernel/process.c:145
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304

read-write to 0xffff888104a443a0 of 8 bytes by task 10 on cpu 1:
process_one_work+0x45f/0x860 kernel/workqueue.c:2606
worker_thread+0x5f2/0xa10 kernel/workqueue.c:2751
kthread+0x1d7/0x210 kernel/kthread.c:389
ret_from_fork+0x2e/0x40 arch/x86/kernel/process.c:145
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304

value changed: 0x0000000000000000 -> 0x0000000000000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 10 Comm: kworker/u4:0 Not tainted 6.5.0-rc5-syzkaller-00182-g25aa0bebba72 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: wg-kex-wg2 wg_packet_handshake_send_worker
==================================================================


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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