From: syzbot <syzbot+c7e665956b189738fe5e@syzkaller.appspotmail.com>
To: eli.billauer@gmail.com, gregkh@linuxfoundation.org,
gustavoars@kernel.org, ingrassia@epigenesys.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
oneukum@suse.com, syzkaller-bugs@googlegroups.com, tiwai@suse.de
Subject: Re: WARNING in cm109_submit_buzz_toggle/usb_submit_urb
Date: Thu, 26 Nov 2020 09:17:15 -0800 [thread overview]
Message-ID: <000000000000270f5805b505b74c@google.com> (raw)
In-Reply-To: <000000000000c19e7b05b4c35440@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: fa02fcd9 Merge tag 'media/v5.10-2' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16d1a88d500000
kernel config: https://syzkaller.appspot.com/x/.config?x=cb8d1a3819ba4356
dashboard link: https://syzkaller.appspot.com/bug?extid=c7e665956b189738fe5e
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ba912d500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10dfad85500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c7e665956b189738fe5e@syzkaller.appspotmail.com
------------[ cut here ]------------
URB 0000000056bd5df7 submitted while active
WARNING: CPU: 0 PID: 8490 at drivers/usb/core/urb.c:378 usb_submit_urb+0x1228/0x14e0 drivers/usb/core/urb.c:378
Modules linked in:
CPU: 0 PID: 8490 Comm: syz-executor949 Not tainted 5.10.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:usb_submit_urb+0x1228/0x14e0 drivers/usb/core/urb.c:378
Code: 89 de e8 6b d6 3b fc 84 db 0f 85 da f4 ff ff e8 4e de 3b fc 4c 89 fe 48 c7 c7 00 57 e1 89 c6 05 01 64 a4 07 01 e8 d4 0c 78 03 <0f> 0b e9 b8 f4 ff ff c7 44 24 14 01 00 00 00 e9 6f f5 ff ff 41 bd
RSP: 0018:ffffc900012ef710 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88802068b480 RSI: ffffffff8158d875 RDI: fffff5200025ded4
RBP: 0000000000000020 R08: 0000000000000001 R09: ffff8880b9e2011b
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880117c3078
R13: 00000000fffffff0 R14: ffffffff85a190a0 R15: ffff88801d38cd00
FS: 0000000001949880(0000) GS:ffff8880b9e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005637666ec160 CR3: 0000000029267000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
cm109_submit_buzz_toggle+0xd0/0x130 drivers/input/misc/cm109.c:351
cm109_toggle_buzzer_async drivers/input/misc/cm109.c:487 [inline]
cm109_input_ev+0x1ea/0x230 drivers/input/misc/cm109.c:621
input_handle_event+0x66e/0x1400 drivers/input/input.c:376
input_inject_event+0x2f5/0x310 drivers/input/input.c:471
kd_sound_helper+0x122/0x260 drivers/tty/vt/keyboard.c:242
input_handler_for_each_handle+0xf4/0x210 drivers/input/input.c:2356
kd_mksound+0x85/0x120 drivers/tty/vt/keyboard.c:266
do_con_trol+0x813/0x54c0 drivers/tty/vt/vt.c:2152
do_con_write+0xb89/0x1dd0 drivers/tty/vt/vt.c:2911
con_write+0x22/0xb0 drivers/tty/vt/vt.c:3255
process_output_block drivers/tty/n_tty.c:595 [inline]
n_tty_write+0x3ce/0xf80 drivers/tty/n_tty.c:2333
do_tty_write drivers/tty/tty_io.c:962 [inline]
tty_write+0x4d9/0x870 drivers/tty/tty_io.c:1046
vfs_write+0x28e/0xa30 fs/read_write.c:603
ksys_write+0x12d/0x250 fs/read_write.c:658
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x444859
Code: e8 bc af 02 00 48 83 c4 18 c3 0f 1f 80 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 0f 83 9b d7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffd082c1508 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000004002e0 RCX: 0000000000444859
RDX: 0000000000001006 RSI: 0000000020001440 RDI: 0000000000000005
RBP: 00000000006d0018 R08: 00000000004002e0 R09: 00000000004002e0
R10: 000000000000000d R11: 0000000000000246 R12: 0000000000402480
R13: 0000000000402510 R14: 0000000000000000 R15: 0000000000000000
next prev parent reply other threads:[~2020-11-26 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 10:05 WARNING in cm109_submit_buzz_toggle/usb_submit_urb syzbot
2020-11-26 17:17 ` syzbot [this message]
2021-01-13 23:01 ` 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:
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=000000000000270f5805b505b74c@google.com \
--to=syzbot+c7e665956b189738fe5e@syzkaller.appspotmail.com \
--cc=eli.billauer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=ingrassia@epigenesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.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.