general protection fault in rcu_sync_func (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d7e5d5321233 UPSTREAM: bpf: Ensure correct locking around ..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=160ed9f5880000
kernel config: https://syzkaller.appspot.com/x/.config?x=c29947a309dbd4d3
dashboard link: https://syzkaller.appspot.com/bug?extid=5a4973c2e1336d3c96a4
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7a4bf9153fd2/disk-d7e5d532.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/38bfe060d114/vmlinux-d7e5d532.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fc129d5a4306/bzImage-d7e5d532.xz

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

kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 885 Comm: syz-executor.1 Not tainted 5.4.219-syzkaller-00096-gd7e5d5321233 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:__wake_up_common kernel/sched/wait.c:81 [inline]
RIP: 0010:__wake_up_locked+0x67/0x120 kernel/sched/wait.c:151
Code: 00 00 fc ff df 4c 8b 73 08 66 2e 0f 1f 84 00 00 00 00 00 4d 39 f5 0f 84 b4 00 00 00 4c 89 f5 49 8d 5e e8 4c 89 f0 48 c1 e8 03 <80> 3c 10 00 74 12 48 89 ef e8 2b c7 48 00 48 ba 00 00 00 00 00 fc
RSP: 0018:ffff8881e3ebf920 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffffffffffffffe8 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000003 RDI: ffff8881e0849c98
RBP: 0000000000000000 R08: dffffc0000000000 R09: 0000000000000003
R10: ffffed103c7d7f19 R11: 1ffff1103c7d7f18 R12: 0000000000000001
R13: ffff8881e0849ca0 R14: 0000000000000000 R15: ffff8881e0849c98
FS: 00007fbee65a0700(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f127000 CR3: 00000001e160e000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
rcu_sync_func+0xaa/0x210 kernel/rcu/sync.c:87
rcu_sync_enter+0x1ea/0x330 kernel/rcu/sync.c:150
percpu_down_write+0x72/0x340 kernel/locking/percpu-rwsem.c:146
hci_uart_tty_close+0x11e/0x220 drivers/bluetooth/hci_ldisc.c:536
tty_ldisc_close drivers/tty/tty_ldisc.c:494 [inline]
tty_ldisc_kill drivers/tty/tty_ldisc.c:642 [inline]
tty_ldisc_hangup+0x4bf/0x6b0 drivers/tty/tty_ldisc.c:761
__tty_hangup+0x64b/0x8b0 drivers/tty/tty_io.c:624
tty_vhangup drivers/tty/tty_io.c:697 [inline]
tty_ioctl+0x630/0xcb0 drivers/tty/tty_io.c:2598
do_vfs_ioctl+0x744/0x1730 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/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Modules linked in:
---[ end trace c617559ade2c8abb ]---
RIP: 0010:__wake_up_common kernel/sched/wait.c:81 [inline]
RIP: 0010:__wake_up_locked+0x67/0x120 kernel/sched/wait.c:151
Code: 00 00 fc ff df 4c 8b 73 08 66 2e 0f 1f 84 00 00 00 00 00 4d 39 f5 0f 84 b4 00 00 00 4c 89 f5 49 8d 5e e8 4c 89 f0 48 c1 e8 03 <80> 3c 10 00 74 12 48 89 ef e8 2b c7 48 00 48 ba 00 00 00 00 00 fc
RSP: 0018:ffff8881e3ebf920 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffffffffffffffe8 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000003 RDI: ffff8881e0849c98
RBP: 0000000000000000 R08: dffffc0000000000 R09: 0000000000000003
R10: ffffed103c7d7f19 R11: 1ffff1103c7d7f18 R12: 0000000000000001
R13: ffff8881e0849ca0 R14: 0000000000000000 R15: ffff8881e0849c98
FS: 00007fbee65a0700(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f127000 CR3: 00000001e160e000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 4 bytes skipped:
0: df 4c 8b 73 fisttps 0x73(%rbx,%rcx,4)
4: 08 66 2e or %ah,0x2e(%rsi)
7: 0f 1f 84 00 00 00 00 nopl 0x0(%rax,%rax,1)
e: 00
f: 4d 39 f5 cmp %r14,%r13
12: 0f 84 b4 00 00 00 je 0xcc
18: 4c 89 f5 mov %r14,%rbp
1b: 49 8d 5e e8 lea -0x18(%r14),%rbx
1f: 4c 89 f0 mov %r14,%rax
22: 48 c1 e8 03 shr $0x3,%rax
* 26: 80 3c 10 00 cmpb $0x0,(%rax,%rdx,1) <-- trapping instruction
2a: 74 12 je 0x3e
2c: 48 89 ef mov %rbp,%rdi
2f: e8 2b c7 48 00 callq 0x48c75f
34: 48 rex.W
35: ba 00 00 00 00 mov $0x0,%edx
3a: 00 fc add %bh,%ah


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.