[syzbot] [kernel?] KMSAN: uninit-value in __schedule (5)

3 views
Skip to first unread message

syzbot

unread,
Apr 10, 2024, 5:12:21 AMApr 10
to b...@alien8.de, dave....@linux.intel.com, h...@zytor.com, linux-...@vger.kernel.org, mi...@redhat.com, syzkall...@googlegroups.com, tg...@linutronix.de, x...@kernel.org
Hello,

syzbot found the following issue on:

HEAD commit: e8b0ccb2a787 Merge tag '9p-for-6.9-rc3' of https://github...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14c4529d180000
kernel config: https://syzkaller.appspot.com/x/.config?x=5112b3f484393436
dashboard link: https://syzkaller.appspot.com/bug?extid=28bdcfc1dab2ffa279a5
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/cf4b0d1e3b2d/disk-e8b0ccb2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/422cac6cc940/vmlinux-e8b0ccb2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a4df48e199b/bzImage-e8b0ccb2.xz

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

Dead loop on virtual device ipvlan1, fix it urgently!
=====================================================
BUG: KMSAN: uninit-value in schedule_debug kernel/sched/core.c:5962 [inline]
BUG: KMSAN: uninit-value in __schedule+0x816/0x6bc0 kernel/sched/core.c:6629
schedule_debug kernel/sched/core.c:5962 [inline]
__schedule+0x816/0x6bc0 kernel/sched/core.c:6629
preempt_schedule_common kernel/sched/core.c:6925 [inline]
__cond_resched+0x49/0xc0 kernel/sched/core.c:8590
_cond_resched include/linux/sched.h:1988 [inline]
process_one_work kernel/workqueue.c:3287 [inline]
process_scheduled_works+0xc19/0x1bd0 kernel/workqueue.c:3335
worker_thread+0xea5/0x1560 kernel/workqueue.c:3416
kthread+0x3e2/0x540 kernel/kthread.c:388
ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243

Local variable _addrs created at:
nf_ct_get_tuple+0x56/0x7d0 net/netfilter/nf_conntrack_core.c:277
resolve_normal_ct net/netfilter/nf_conntrack_core.c:1822 [inline]
nf_conntrack_in+0x5cd/0x30d0 net/netfilter/nf_conntrack_core.c:1996

CPU: 0 PID: 5088 Comm: kworker/0:4 Tainted: G W 6.9.0-rc2-syzkaller-00207-ge8b0ccb2a787 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: mld mld_ifc_work
=====================================================


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