From: syzbot <syzbot+621d4ae5dc548c7ac3f6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: [syzbot] upstream boot error: general protection fault in timerqueue_del
Date: Tue, 16 Aug 2022 01:40:24 -0700 [thread overview]
Message-ID: <0000000000000f266f05e657b373@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 4a9350597aff Merge tag 'sound-fix-6.0-rc1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1249c047080000
kernel config: https://syzkaller.appspot.com/x/.config?x=4757943c2b26daff
dashboard link: https://syzkaller.appspot.com/bug?extid=621d4ae5dc548c7ac3f6
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+621d4ae5dc548c7ac3f6@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffdffe0000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x00000fff00000000-0x00000fff00000007]
CPU: 0 PID: 1108 Comm: kworker/u4:3 Not tainted 5.19.0-syzkaller-14090-g4a9350597aff #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:timerqueue_del+0x26/0xf0 lib/timerqueue.c:55
Code: 0f 1f 40 00 55 41 57 41 56 41 55 41 54 53 49 89 f5 49 89 fe 48 bd 00 00 00 00 00 fc ff df e8 21 3a 20 fd 4d 89 ec 49 c1 ec 03 <41> 80 3c 2c 00 74 08 4c 89 ef e8 cb d8 73 fd 49 8b 5d 00 48 89 df
RSP: 0000:ffffc90004ebfc30 EFLAGS: 00010006
RAX: ffffffff846958af RBX: 00000fff00000000 RCX: ffff888020858000
RDX: 0000000000000000 RSI: 00000fff00000000 RDI: ffff8880207744d8
RBP: dffffc0000000000 R08: dffffc0000000000 R09: fffff520009d7f84
R10: fffff520009d7f85 R11: 1ffff920009d7f84 R12: 000001ffe0000000
R13: 00000fff00000000 R14: ffff8880207744d8 R15: ffff8880207744d8
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000ca8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
cleanup_timerqueue kernel/time/posix-cpu-timers.c:519 [inline]
cleanup_timers kernel/time/posix-cpu-timers.c:534 [inline]
posix_cpu_timers_exit_group+0x7b/0x200 kernel/time/posix-cpu-timers.c:550
__exit_signal kernel/exit.c:109 [inline]
release_task+0x5b8/0x1890 kernel/exit.c:203
exit_notify kernel/exit.c:708 [inline]
do_exit+0x16ac/0x20a0 kernel/exit.c:815
call_usermodehelper_exec_async+0x3a1/0x3b0 kernel/umh.c:125
ret_from_fork+0x1f/0x30
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:timerqueue_del+0x26/0xf0 lib/timerqueue.c:55
Code: 0f 1f 40 00 55 41 57 41 56 41 55 41 54 53 49 89 f5 49 89 fe 48 bd 00 00 00 00 00 fc ff df e8 21 3a 20 fd 4d 89 ec 49 c1 ec 03 <41> 80 3c 2c 00 74 08 4c 89 ef e8 cb d8 73 fd 49 8b 5d 00 48 89 df
RSP: 0000:ffffc90004ebfc30 EFLAGS: 00010006
RAX: ffffffff846958af RBX: 00000fff00000000 RCX: ffff888020858000
RDX: 0000000000000000 RSI: 00000fff00000000 RDI: ffff8880207744d8
RBP: dffffc0000000000 R08: dffffc0000000000 R09: fffff520009d7f84
R10: fffff520009d7f85 R11: 1ffff920009d7f84 R12: 000001ffe0000000
R13: 00000fff00000000 R14: ffff8880207744d8 R15: ffff8880207744d8
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000ca8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 0f 1f 40 00 nopl 0x0(%rax)
4: 55 push %rbp
5: 41 57 push %r15
7: 41 56 push %r14
9: 41 55 push %r13
b: 41 54 push %r12
d: 53 push %rbx
e: 49 89 f5 mov %rsi,%r13
11: 49 89 fe mov %rdi,%r14
14: 48 bd 00 00 00 00 00 movabs $0xdffffc0000000000,%rbp
1b: fc ff df
1e: e8 21 3a 20 fd callq 0xfd203a44
23: 4d 89 ec mov %r13,%r12
26: 49 c1 ec 03 shr $0x3,%r12
* 2a: 41 80 3c 2c 00 cmpb $0x0,(%r12,%rbp,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 ef mov %r13,%rdi
34: e8 cb d8 73 fd callq 0xfd73d904
39: 49 8b 5d 00 mov 0x0(%r13),%rbx
3d: 48 89 df mov %rbx,%rdi
---
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.
reply other threads:[~2022-08-16 8:40 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=0000000000000f266f05e657b373@google.com \
--to=syzbot+621d4ae5dc548c7ac3f6@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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 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.