From: syzbot <syzbot+150f793ac5bc18eee150@syzkaller.appspotmail.com>
To: dmitry.torokhov@gmail.com, eli.billauer@gmail.com,
gregkh@linuxfoundation.org, gustavoars@kernel.org,
ingrassia@epigenesys.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
vulab@iscas.ac.cn
Subject: Re: WARNING in cm109_input_ev/usb_submit_urb
Date: Wed, 02 Dec 2020 20:57:16 -0800 [thread overview]
Message-ID: <000000000000a023c905b588314b@google.com> (raw)
In-Reply-To: <000000000000f6530105b48b2816@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 3bb61aa6 Merge tag 'arm64-fixes' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10837e9d500000
kernel config: https://syzkaller.appspot.com/x/.config?x=c3904d1cc0af152
dashboard link: https://syzkaller.appspot.com/bug?extid=150f793ac5bc18eee150
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12b9c19d500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c422e3500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+150f793ac5bc18eee150@syzkaller.appspotmail.com
------------[ cut here ]------------
URB 00000000fa7e6a0b submitted while active
WARNING: CPU: 0 PID: 8462 at drivers/usb/core/urb.c:378 usb_submit_urb+0xf57/0x1510 drivers/usb/core/urb.c:378
Modules linked in:
CPU: 0 PID: 8462 Comm: syz-executor064 Not tainted 5.10.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:usb_submit_urb+0xf57/0x1510 drivers/usb/core/urb.c:378
Code: 5c 41 5d 41 5e 41 5f 5d e9 76 5b ff ff e8 c1 e9 04 fc c6 05 45 10 8b 07 01 48 c7 c7 a0 b6 5b 8a 4c 89 e6 31 c0 e8 69 08 d5 fb <0f> 0b e9 20 f1 ff ff e8 9d e9 04 fc eb 05 e8 96 e9 04 fc bb a6 ff
RSP: 0018:ffffc90000ecf6d8 EFLAGS: 00010046
RAX: ed1497fd940bbe00 RBX: ffff8880113d2108 RCX: ffff88801b269a40
RDX: 0000000000000000 RSI: 0000000080000002 RDI: 0000000000000000
RBP: 0000000000000a20 R08: ffffffff815d29e2 R09: ffffed1017383ffc
R10: ffffed1017383ffc R11: 0000000000000000 R12: ffff8880113d2100
R13: dffffc0000000000 R14: dffffc0000000000 R15: ffff88801d001850
FS: 00000000013ac880(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000558946f0cf78 CR3: 0000000011c70000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
cm109_submit_buzz_toggle drivers/input/misc/cm109.c:351 [inline]
cm109_toggle_buzzer_async drivers/input/misc/cm109.c:487 [inline]
cm109_input_ev+0x1dc/0x3a0 drivers/input/misc/cm109.c:621
input_handle_event+0x895/0x1510 drivers/input/input.c:376
input_inject_event+0x1e8/0x280 drivers/input/input.c:471
kd_sound_helper+0xfc/0x200 drivers/tty/vt/keyboard.c:242
input_handler_for_each_handle+0xc8/0x160 drivers/input/input.c:2356
kd_mksound+0x6c/0x140 drivers/tty/vt/keyboard.c:266
do_con_trol drivers/tty/vt/vt.c:2152 [inline]
do_con_write+0x3325/0xdee0 drivers/tty/vt/vt.c:2911
con_write+0x20/0x40 drivers/tty/vt/vt.c:3255
process_output_block drivers/tty/n_tty.c:595 [inline]
n_tty_write+0xcc2/0x1160 drivers/tty/n_tty.c:2333
do_tty_write drivers/tty/tty_io.c:962 [inline]
tty_write+0x585/0x8f0 drivers/tty/tty_io.c:1046
vfs_write+0x220/0xab0 fs/read_write.c:603
ksys_write+0x11b/0x220 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:0x444839
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:00007ffeb806aaf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000004002e0 RCX: 0000000000444839
RDX: 0000000000001006 RSI: 00000000200002c0 RDI: 0000000000000005
RBP: 00000000006d0018 R08: 00000000004002e0 R09: 00000000004002e0
R10: 000000000000000d R11: 0000000000000246 R12: 0000000000402460
R13: 00000000004024f0 R14: 0000000000000000 R15: 0000000000000000
next prev parent reply other threads:[~2020-12-03 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 15:04 WARNING in cm109_input_ev/usb_submit_urb syzbot
2020-12-03 4:57 ` syzbot [this message]
2020-12-10 4:23 ` Dmitry Torokhov
2020-12-10 13:38 ` 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=000000000000a023c905b588314b@google.com \
--to=syzbot+150f793ac5bc18eee150@syzkaller.appspotmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eli.billauer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=ingrassia@epigenesys.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vulab@iscas.ac.cn \
/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.