From: syzbot <syzbot+8974d7bf41172a2b0729@syzkaller.appspotmail.com>
To: anna-maria@linutronix.de, frederic@kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: [syzbot] [kernel?] KMSAN: uninit-value in timerqueue_add (2)
Date: Tue, 10 Dec 2024 10:20:26 -0800 [thread overview]
Message-ID: <6758866a.050a0220.a30f1.01d9.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: b8f52214c61a Merge tag 'audit-pr-20241205' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b6d330580000
kernel config: https://syzkaller.appspot.com/x/.config?x=dcc2c6db74766fbc
dashboard link: https://syzkaller.appspot.com/bug?extid=8974d7bf41172a2b0729
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/961b446be7db/disk-b8f52214.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9f408f31c5b2/vmlinux-b8f52214.xz
kernel image: https://storage.googleapis.com/syzbot-assets/97900576aa59/bzImage-b8f52214.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8974d7bf41172a2b0729@syzkaller.appspotmail.com
ffff88813fd05fc0: ffff888031cf2978 (0xffff888031cf2978)
ffff88813fd05fc8: 0000000000000000 ...
ffff88813fd05fe8: ffff888031cf2968 (0xffff888031cf2968)
ffff88813fd05ff0: ffffffff8fe8d40e (instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1049 [inline])
ffff88813fd05ff0: ffffffff8fe8d40e (sysvec_apic_timer_interrupt+0x7e/0x90 arch/x86/kernel/apic/apic.c:1049)
ffff88813fd05ff8: ffff888031cf2958 (0xffff888031cf2958)
BUG: KMSAN: uninit-value in rb_add_cached include/linux/rbtree.h:172 [inline]
BUG: KMSAN: uninit-value in timerqueue_add+0x20b/0x3d0 lib/timerqueue.c:40
rb_add_cached include/linux/rbtree.h:172 [inline]
timerqueue_add+0x20b/0x3d0 lib/timerqueue.c:40
enqueue_hrtimer+0x189/0x3a0 kernel/time/hrtimer.c:1084
__run_hrtimer kernel/time/hrtimer.c:1756 [inline]
__hrtimer_run_queues+0x64d/0xe40 kernel/time/hrtimer.c:1803
hrtimer_interrupt+0x41b/0xb10 kernel/time/hrtimer.c:1865
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1038 [inline]
__sysvec_apic_timer_interrupt+0xa7/0x420 arch/x86/kernel/apic/apic.c:1055
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1049 [inline]
sysvec_apic_timer_interrupt+0x7e/0x90 arch/x86/kernel/apic/apic.c:1049
Uninit was created at:
__alloc_pages_noprof+0x9a7/0xe00 mm/page_alloc.c:4774
alloc_pages_mpol_noprof+0x299/0x990 mm/mempolicy.c:2265
alloc_pages_noprof+0x1bf/0x1e0 mm/mempolicy.c:2344
alloc_slab_page mm/slub.c:2408 [inline]
allocate_slab+0x320/0x12e0 mm/slub.c:2574
new_slab mm/slub.c:2627 [inline]
___slab_alloc+0x12ef/0x35e0 mm/slub.c:3815
__slab_alloc mm/slub.c:3905 [inline]
__slab_alloc_node mm/slub.c:3980 [inline]
slab_alloc_node mm/slub.c:4141 [inline]
kmem_cache_alloc_node_noprof+0x84a/0xe00 mm/slub.c:4205
__alloc_skb+0x1e9/0x7b0 net/core/skbuff.c:668
alloc_skb include/linux/skbuff.h:1323 [inline]
new_skb+0x46/0x560 drivers/block/aoe/aoecmd.c:66
aoecmd_cfg_pkts drivers/block/aoe/aoecmd.c:430 [inline]
aoecmd_cfg+0x2c0/0xac0 drivers/block/aoe/aoecmd.c:1370
discover_timer+0x62/0x80 drivers/block/aoe/aoemain.c:25
call_timer_fn+0x49/0x580 kernel/time/timer.c:1793
expire_timers kernel/time/timer.c:1844 [inline]
__run_timers kernel/time/timer.c:2418 [inline]
__run_timer_base+0x84e/0xe90 kernel/time/timer.c:2430
run_timer_base kernel/time/timer.c:2439 [inline]
run_timer_softirq+0x3a/0x70 kernel/time/timer.c:2449
handle_softirqs+0x1a0/0x7c0 kernel/softirq.c:554
__do_softirq+0x14/0x1a kernel/softirq.c:588
CPU: 1 UID: 0 PID: 8505 Comm: syz.1.784 Not tainted 6.13.0-rc1-syzkaller-00182-gb8f52214c61a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
=====================================================
---
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
reply other threads:[~2024-12-10 18:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6758866a.050a0220.a30f1.01d9.GAE@google.com \
--to=syzbot+8974d7bf41172a2b0729@syzkaller.appspotmail.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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