[Android 5.10] BUG: using smp_processor_id() in preemptible code in usbnet_skb_return (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e5e5644ea27f Revert "udf: Avoid excessive partition lengths"
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1078565f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b4a7b8638c3099
dashboard link: https://syzkaller.appspot.com/bug?extid=5698af965beba119b090
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14447287980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1478565f980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0a4309df0fe8/disk-e5e5644e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e5a70844d43b/vmlinux-e5e5644e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/985df9651f99/bzImage-e5e5644e.xz

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

BUG: using smp_processor_id() in preemptible [00000000] code: dhcpcd/133
caller is debug_smp_processor_id+0x17/0x20 lib/smp_processor_id.c:59
CPU: 0 PID: 133 Comm: dhcpcd Not tainted 5.10.226-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118
dump_stack+0x15/0x17 lib/dump_stack.c:135
check_preemption_disabled+0xf2/0x100 lib/smp_processor_id.c:48
debug_smp_processor_id+0x17/0x20 lib/smp_processor_id.c:59
usbnet_skb_return+0x48/0x270 drivers/net/usb/usbnet.c:306
usbnet_resume_rx+0x4d/0xd0 drivers/net/usb/usbnet.c:679
usbnet_change_mtu+0x4ed/0x670 drivers/net/usb/usbnet.c:392
__dev_set_mtu net/core/dev.c:8600 [inline]
dev_set_mtu_ext+0x43c/0x670 net/core/dev.c:8653
dev_set_mtu+0xa0/0x180 net/core/dev.c:8677
dev_ifsioc+0x3a2/0xae0 net/core/dev_ioctl.c:237
dev_ioctl+0x526/0xb40 net/core/dev_ioctl.c:481
sock_do_ioctl+0x295/0x3a0 net/socket.c:1090
sock_ioctl+0x4a6/0x760 net/socket.c:1207
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl+0x114/0x190 fs/ioctl.c:739
__x64_sys_ioctl+0x7b/0x90 fs/ioctl.c:739
do_syscall_64+0x34/0x70
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f24d46dcd49
Code: 5c c3 48 8d 44 24 08 48 89 54 24 e0 48 89 44 24 c0 48 8d 44 24 d0 48 89 44 24 c8 b8 10 00 00 00 c7 44 24 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 76 10 48 8b 15 ae 60 0d 00 f7 d8 41 83 c8
RSP: 002b:00007ffc80db7a68 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f24d460e6c0 RCX: 00007f24d46dcd49
RDX: 00007ffc80dc7c58 RSI: 0000000000008922 RDI: 0000000000000012
RBP: 00007ffc80dd7e18 R08: 00007ffc80dc7c18 R09: 00007ffc80dc7bc8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc80dc7c58 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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.