All of
 help / color / mirror / Atom feed
From: syzbot <>
Subject: [syzbot] WARNING in hrtimer_init
Date: Mon, 08 Aug 2022 07:49:24 -0700	[thread overview]
Message-ID: <> (raw)


syzbot found the following issue on:

HEAD commit:    200e340f2196 Merge tag 'pull-work.dcache' of git://git.ker..
git tree:       upstream
kernel config:
dashboard link:
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:
C reproducer:

The issue was bisected to:

commit 536395260582be7443b0b35b0bbb89ffe3947f62
Author: Joao Martins <>
Date:   Thu Mar 3 15:41:22 2022 +0000

    KVM: x86/xen: handle PV timers oneshot mode

bisection log:
final oops:
console output:

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Fixes: 536395260582 ("KVM: x86/xen: handle PV timers oneshot mode")

L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and for details.
------------[ cut here ]------------
ODEBUG: init active (active state 0) object type: hrtimer hint: xen_timer_callback+0x0/0xb0 include/linux/rcupdate.h:281
WARNING: CPU: 1 PID: 3601 at lib/debugobjects.c:505 debug_print_object lib/debugobjects.c:502 [inline]
WARNING: CPU: 1 PID: 3601 at lib/debugobjects.c:505 __debug_object_init+0xae3/0x1860 lib/debugobjects.c:590
Modules linked in:
CPU: 1 PID: 3601 Comm: syz-executor171 Not tainted 5.19.0-syzkaller-02972-g200e340f2196 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:debug_print_object lib/debugobjects.c:502 [inline]
RIP: 0010:__debug_object_init+0xae3/0x1860 lib/debugobjects.c:590
Code: 89 ff e8 40 6e a5 fd 4d 8b 07 48 c7 c7 60 b0 e9 8a 48 c7 c6 c0 ae e9 8a 48 89 da 44 89 f1 4c 8b 4c 24 18 31 c0 e8 2d d6 1a fd <0f> 0b 4c 8b 64 24 48 ff 05 4c 7f ce 09 48 8b 9c 24 b0 00 00 00 48
RSP: 0018:ffffc900030df3a0 EFLAGS: 00010246
RAX: 1a852b5f5a7fcb00 RBX: ffffffff8ae9b1c0 RCX: ffff888027671d80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900030df588 R08: ffffffff816c1ccd R09: fffff5200061bdf1
R10: fffff5200061bdf1 R11: 1ffff9200061bdf0 R12: ffff88802733af2c
R13: dffffc0000000000 R14: 0000000000000000 R15: ffffffff8a8f8840
FS:  0000555556fce300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055e1f0266048 CR3: 000000001fc5d000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 debug_hrtimer_init kernel/time/hrtimer.c:414 [inline]
 debug_init kernel/time/hrtimer.c:468 [inline]
 hrtimer_init+0x20/0x40 kernel/time/hrtimer.c:1592
 kvm_xen_init_timer arch/x86/kvm/xen.c:168 [inline]
 kvm_xen_vcpu_set_attr+0x82c/0x11a0 arch/x86/kvm/xen.c:716
 kvm_arch_vcpu_ioctl+0x1651/0x2680 arch/x86/kvm/x86.c:5715
 kvm_vcpu_ioctl+0x6d5/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4104
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
RIP: 0033:0x7fc97e717e99
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe56856698 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc97e717e99
RDX: 0000000020000000 RSI: 000000004048aecb RDI: 0000000000000007
RBP: 00007fc97e6dbdb0 R08: 0000000000000012 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc97e6dbe40
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000

This report is generated by a bot. It may contain errors.
See for more information about syzbot.
syzbot engineers can be reached at

syzbot will keep track of this issue. See: for how to communicate with syzbot.
For information about bisection process see:
syzbot can test patches for this issue, for details see:

             reply	other threads:[~2022-08-08 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 14:49 syzbot [this message]
     [not found] <>
2022-08-09 20:18 ` [syzbot] WARNING in hrtimer_init syzbot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.