All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c81440130f8669eb86d8@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bp@alien8.de,
	dave.hansen@linux.intel.com, hpa@zytor.com,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	swboyd@chromium.org, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de, x86@kernel.org
Subject: [syzbot] WARNING in console_unlock
Date: Sat, 18 Dec 2021 06:49:25 -0800	[thread overview]
Message-ID: <0000000000000dfd4605d36cc33b@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    ea922272cbe5 Add linux-next specific files for 20211210
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12517ef5b00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a2b5499ad0143759
dashboard link: https://syzkaller.appspot.com/bug?extid=c81440130f8669eb86d8
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

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

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
Modules linked in:
------------[ cut here ]------------
WARNING: CPU: 1 PID: 9308 at include/trace/events/printk.h:10 trace_console_rcuidle include/trace/events/printk.h:10 [inline]
WARNING: CPU: 1 PID: 9308 at include/trace/events/printk.h:10 call_console_drivers kernel/printk/printk.c:1905 [inline]
WARNING: CPU: 1 PID: 9308 at include/trace/events/printk.h:10 console_unlock+0xabd/0xb70 kernel/printk/printk.c:2714
Modules linked in:
CPU: 1 PID: 9308 Comm: syz-executor.2 Not tainted 5.16.0-rc4-next-20211210-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:trace_console_rcuidle include/trace/events/printk.h:10 [inline]
RIP: 0010:call_console_drivers kernel/printk/printk.c:1905 [inline]
RIP: 0010:console_unlock+0xabd/0xb70 kernel/printk/printk.c:2714
Code: e3 ef 0e 00 00 00 00 48 8b bc 24 68 01 00 00 e8 69 c7 ff ff e9 35 ff ff ff e8 1f e7 18 00 0f 0b e9 17 fd ff ff e8 13 e7 18 00 <0f> 0b e9 6a fd ff ff 48 89 ef e8 24 df 63 00 e9 34 f7 ff ff e8 ea
RSP: 0018:fffffe0000053d40 EFLAGS: 00010046
RAX: 0000000080110000 RBX: 0000000000100000 RCX: 0000000000000000
RDX: ffff88801b238000 RSI: ffffffff815f146d RDI: 0000000000000003
RBP: fffffe0000053dd8 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff815f11d6 R11: 0000000000000000 R12: 000000000000000f
R13: 0000000000000000 R14: fffffe0000053d98 R15: dffffc0000000000
FS:  00007f83f79b2700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 000000004313c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <#DF>
 console_unblank+0xfc/0x130 kernel/printk/printk.c:2779
 bust_spinlocks+0x60/0xe0 lib/bust_spinlocks.c:28
 oops_end+0x2b/0xf0 arch/x86/kernel/dumpstack.c:361
 exc_double_fault+0x16d/0x180 arch/x86/kernel/traps.c:466
 asm_exc_double_fault+0x1e/0x40 arch/x86/include/asm/idtentry.h:613
RIP: 0010:entry_SYSENTER_compat+0x3/0x17 arch/x86/entry/entry_64_compat.S:54
Code: 41 5c 5d 5b 41 5b 41 5a 41 59 41 58 58 59 5a 5e 5f 48 83 c4 30 fd 48 c7 44 24 28 00 00 00 00 48 cf cc cc cc cc cc cc 0f 01 f8 <50> 58 65 48 8b 24 25 10 70 02 00 6a 2b 6a 00 9c 6a 23 6a 00 89 c0
RSP: 0018:0000000000000000 EFLAGS: 00010046
RAX: 00000000000000d0 RBX: 0000000000018ff5 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000200193c0 R08: 0000000000000000 R09: 0000000020000280
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </#DF>
----------------
Code disassembly (best guess):
   0:	41 5c                	pop    %r12
   2:	5d                   	pop    %rbp
   3:	5b                   	pop    %rbx
   4:	41 5b                	pop    %r11
   6:	41 5a                	pop    %r10
   8:	41 59                	pop    %r9
   a:	41 58                	pop    %r8
   c:	58                   	pop    %rax
   d:	59                   	pop    %rcx
   e:	5a                   	pop    %rdx
   f:	5e                   	pop    %rsi
  10:	5f                   	pop    %rdi
  11:	48 83 c4 30          	add    $0x30,%rsp
  15:	fd                   	std
  16:	48 c7 44 24 28 00 00 	movq   $0x0,0x28(%rsp)
  1d:	00 00
  1f:	48 cf                	iretq
  21:	cc                   	int3
  22:	cc                   	int3
  23:	cc                   	int3
  24:	cc                   	int3
  25:	cc                   	int3
  26:	cc                   	int3
  27:	0f 01 f8             	swapgs
* 2a:	50                   	push   %rax <-- trapping instruction
  2b:	58                   	pop    %rax
  2c:	65 48 8b 24 25 10 70 	mov    %gs:0x27010,%rsp
  33:	02 00
  35:	6a 2b                	pushq  $0x2b
  37:	6a 00                	pushq  $0x0
  39:	9c                   	pushfq
  3a:	6a 23                	pushq  $0x23
  3c:	6a 00                	pushq  $0x0
  3e:	89 c0                	mov    %eax,%eax


---
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:[~2021-12-18 14:49 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=0000000000000dfd4605d36cc33b@google.com \
    --to=syzbot+c81440130f8669eb86d8@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=swboyd@chromium.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.