BUG: using smp_processor_id() in preemptible code in usbnet_skb_return

6 views
Skip to first unread message

syzbot

unread,
Mar 28, 2022, 11:59:28 PM3/28/22
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ed043095f483 ANDROID: usb: gadget: f_accessory: add compat..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=171e5f39700000
kernel config: https://syzkaller.appspot.com/x/.config?x=99f84aafede1456a
dashboard link: https://syzkaller.appspot.com/bug?extid=d062e7b7d76a11f049bb
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e9fe07700000

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

BUG: using smp_processor_id() in preemptible [00000000] code: dhcpcd/193
caller is usbnet_skb_return+0x45/0x210 drivers/net/usb/usbnet.c:310
CPU: 1 PID: 193 Comm: dhcpcd Not tainted 5.4.180-syzkaller-00087-ged043095f483 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x18e/0x1de lib/dump_stack.c:118
check_preemption_disabled+0x270/0x2c0 lib/smp_processor_id.c:47
usbnet_skb_return+0x45/0x210 drivers/net/usb/usbnet.c:310
usbnet_resume_rx+0x4b/0xd0 drivers/net/usb/usbnet.c:683
usbnet_change_mtu+0x4b2/0x630 drivers/net/usb/usbnet.c:396
__dev_set_mtu net/core/dev.c:8010 [inline]
dev_set_mtu_ext+0x33d/0x740 net/core/dev.c:8063
dev_set_mtu+0x43/0xf0 net/core/dev.c:8087
dev_ifsioc+0x2eb/0x960 net/core/dev_ioctl.c:233
dev_ioctl+0x4b3/0xab0 net/core/dev_ioctl.c:483
sock_do_ioctl+0x1d8/0x2f0 net/socket.c:1062
sock_ioctl+0x47c/0x6b0 net/socket.c:1179
do_vfs_ioctl+0x6fb/0x15b0 fs/ioctl.c:47
ksys_ioctl fs/ioctl.c:742 [inline]
__do_sys_ioctl fs/ioctl.c:749 [inline]
__se_sys_ioctl fs/ioctl.c:747 [inline]
__x64_sys_ioctl+0xd4/0x110 fs/ioctl.c:747
do_syscall_64+0xcb/0x1e0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7fc3481b60e7
Code: 3c 1c e8 1c ff ff ff 85 c0 79 87 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 61 9d 0c 00 f7 d8 64 89 01 48
RSP: 002b:00007ffff5877008 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fc3480c86c8 RCX: 00007fc3481b60e7
RDX: 00007ffff58871f8 RSI: 0000000000008922 RDI: 000000000000000e
RBP: 00007ffff58973a8 R08: 00007ffff58871b8 R09: 00007ffff5887168
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffff58871f8 R14: 0000000000000028 R15: 0000000000008922


---
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 syzk...@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

syzbot

unread,
Oct 9, 2023, 9:39:38 AM10/9/23
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages