From: syzbot <syzbot+ab02336a647181a886a6@syzkaller.appspotmail.com>
To: benjamin.tissoires@redhat.com, jikos@kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: WARNING in hid_alloc_report_buf
Date: Tue, 23 Feb 2021 00:06:21 -0800 [thread overview]
Message-ID: <000000000000dc095b05bbfc6421@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f40ddce8 Linux 5.11
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c5a17f500000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b919ebed7b4902
dashboard link: https://syzkaller.appspot.com/bug?extid=ab02336a647181a886a6
compiler: Debian clang version 11.0.1-2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=138bde22d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13b82c12d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ab02336a647181a886a6@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 8428 at mm/page_alloc.c:4979 __alloc_pages_nodemask+0x44e/0x500 mm/page_alloc.c:5023
Modules linked in:
CPU: 1 PID: 8428 Comm: syz-executor094 Not tainted 5.11.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__alloc_pages_nodemask+0x44e/0x500 mm/page_alloc.c:5023
Code: 00 48 ba 00 00 00 00 00 fc ff df e9 fb fd ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 06 fe ff ff e8 c7 53 09 00 e9 fc fd ff ff <0f> 0b e9 15 fe ff ff 44 89 ed a9 00 00 08 00 75 11 81 e5 7f ff ff
RSP: 0018:ffffc90001ad7c40 EFLAGS: 00010046
RAX: ffffc90001ad7c48 RBX: ffffc90001ad7c74 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc90001ad7c70
RBP: 0000000000000000 R08: dffffc0000000000 R09: ffffc90001ad7c48
R10: fffff5200035af8e R11: 0000000000000000 R12: 0000000020000007
R13: 0000000000040a20 R14: 1ffff9200035af8e R15: 0000000000000012
FS: 0000000001255300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005573bf3240c0 CR3: 0000000013416000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
alloc_pages include/linux/gfp.h:547 [inline]
kmalloc_order+0x40/0x130 mm/slab_common.c:837
kmalloc_order_trace+0x15/0x70 mm/slab_common.c:853
kmalloc_large include/linux/slab.h:481 [inline]
__kmalloc+0x257/0x330 mm/slub.c:3974
kmalloc include/linux/slab.h:557 [inline]
hid_alloc_report_buf+0x70/0xa0 drivers/hid/hid-core.c:1648
__usbhid_submit_report drivers/hid/usbhid/hid-core.c:590 [inline]
usbhid_submit_report+0x3c6/0xa10 drivers/hid/usbhid/hid-core.c:640
hid_hw_request include/linux/hid.h:1072 [inline]
hiddev_ioctl+0x196c/0x2780 drivers/hid/usbhid/hiddev.c:726
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl+0xfb/0x170 fs/ioctl.c:739
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x444659
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 14 00 00 90 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:00007fff05ace6d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000004004a0 RCX: 0000000000444659
RDX: 0000000020000080 RSI: 00000000400c4808 RDI: 0000000000000004
RBP: 0000000000403ee0 R08: 0000000000000001 R09: 00000000004004a0
R10: 000000000000001f R11: 0000000000000246 R12: 0000000000403f70
R13: 0000000000000000 R14: 00000000004b2018 R15: 00000000004004a0
---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2021-02-23 8:08 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=000000000000dc095b05bbfc6421@google.com \
--to=syzbot+ab02336a647181a886a6@syzkaller.appspotmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).