[Android 6.1] BUG: scheduling while atomic in do_sys_poll

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 26f2c9be9ebe UPSTREAM: netfilter: nf_tables: mark set as d..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=15e1fa63180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7bd1a415c6de5d9d
dashboard link: https://syzkaller.appspot.com/bug?extid=3b792e8b261b2ba44906
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=164a33fb180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111f0bf3180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6b9937ef8f7b/disk-26f2c9be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1b0f979a35e/vmlinux-26f2c9be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84a3524b4845/bzImage-26f2c9be.xz

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

BUG: scheduling while atomic: sshd/284/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff83ff8840>] spin_lock_bh include/linux/spinlock.h:355 [inline]
[<ffffffff83ff8840>] release_sock+0x30/0x1b0 net/core/sock.c:3512
CPU: 1 PID: 284 Comm: sshd Not tainted 6.1.75-syzkaller-00025-g26f2c9be9ebe #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x1b lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5960
schedule_debug kernel/sched/core.c:5987 [inline]
__schedule+0xcf7/0x1550 kernel/sched/core.c:6622
schedule+0xc3/0x180 kernel/sched/core.c:6805
schedule_hrtimeout_range_clock+0x1ef/0x360 kernel/time/hrtimer.c:2307
schedule_hrtimeout_range+0x2a/0x40 kernel/time/hrtimer.c:2353
poll_schedule_timeout fs/select.c:244 [inline]
do_poll fs/select.c:966 [inline]
do_sys_poll+0xdd7/0x1230 fs/select.c:1016
__do_sys_ppoll fs/select.c:1122 [inline]
__se_sys_ppoll+0x29c/0x330 fs/select.c:1102
__x64_sys_ppoll+0xbf/0xd0 fs/select.c:1102
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f862bb19ad5
Code: 85 d2 74 0d 0f 10 02 48 8d 54 24 20 0f 11 44 24 20 64 8b 04 25 18 00 00 00 85 c0 75 27 41 b8 08 00 00 00 b8 0f 01 00 00 0f 05 <48> 3d 00 f0 ff ff 76 75 48 8b 15 24 73 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffc257bc880 EFLAGS: 00000246 ORIG_RAX: 000000000000010f
RAX: ffffffffffffffda RBX: 00000000000668a0 RCX: 00007f862bb19ad5
RDX: 00007ffc257bc8a0 RSI: 0000000000000004 RDI: 000055e2d9f1b840
RBP: 000055e2d9f1a410 R08: 0000000000000008 R09: 0000000000000000
R10: 00007ffc257bc988 R11: 0000000000000246 R12: 000055e2d9101aa4
R13: 0000000000000001 R14: 000055e2d91023e8 R15: 00007ffc257bc908
</TASK>
BUG: scheduling while atomic: sshd/284/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff83ff8840>] spin_lock_bh include/linux/spinlock.h:355 [inline]
[<ffffffff83ff8840>] release_sock+0x30/0x1b0 net/core/sock.c:3512
CPU: 1 PID: 284 Comm: sshd Tainted: G W 6.1.75-syzkaller-00025-g26f2c9be9ebe #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x1b lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5960
schedule_debug kernel/sched/core.c:5987 [inline]
__schedule+0xcf7/0x1550 kernel/sched/core.c:6622
schedule+0xc3/0x180 kernel/sched/core.c:6805
exit_to_user_mode_loop+0x4e/0xa0 kernel/entry/common.c:159
exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x26/0x140 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f862bac2773
Code: 00 f3 a5 48 8d 74 24 88 48 b9 ff ff ff 7f fe ff ff ff 48 21 c8 48 89 44 24 88 41 ba 08 00 00 00 44 89 c7 b8 0e 00 00 00 0f 05 <45> 31 c0 3d 00 f0 ff ff 76 06 41 89 c0 41 f7 d8 44 89 c0 5a c3 41
RSP: 002b:00007ffc257bc8a0 EFLAGS: 00000246 ORIG_RAX: 000000000000000e
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f862bac2773
RDX: 00007ffc257bc988 RSI: 00007ffc257bc908 RDI: 0000000000000000
RBP: 000055e2d9f1a410 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000246 R12: 000055e2d9101aa4
R13: 000000000000001c R14: 000055e2d91023e8 R15: 00007ffc257bc908
</TASK>


---
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