general protection fault in rb_next

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 301f935be9e0 sch_cake: Fix tin order when set through skb-..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=106cc252400000
kernel config: https://syzkaller.appspot.com/x/.config?x=89129667b46496c3
dashboard link: https://syzkaller.appspot.com/bug?extid=362e97632f7c603c8a11
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [linux-...@vger.kernel.org tg...@linutronix.de]

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

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+362e97...@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] SMP KASAN
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.18.0-rc3+ #56
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:rb_next+0xd7/0x140 lib/rbtree.c:541
Code: 49 89 dc 4c 89 eb 48 83 e3 fc 48 89 d8 75 c8 48 83 c4 08 5b 41 5c 41
5d 41 5e 5d c3 48 89 d0 48 8d 78 10 48 89 fa 48 c1 ea 03 <80> 3c 1a 00 75
1a 48 8b 50 10 48 85 d2 75 e3 48 83 c4 08 5b 41 5c
RSP: 0018:ffff8801d9af7ae0 EFLAGS: 00010007
RAX: 23b1e8c689c389ff RBX: dffffc0000000000 RCX: ffffffff8792d801
RDX: 04763d18d1387141 RSI: ffffffff8792d890 RDI: 23b1e8c689c38a0f
RBP: ffff8801d9af7b08 R08: ffff8801d9ae8380 R09: fffffbfff156f2e9
R10: fffffbfff156f2e9 R11: ffffffff8ab7974b R12: ffff8801daf26560
R13: ffff8801ca0878c1 R14: dffffc0000000000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f80ca03ddb8 CR3: 00000001a2003000 CR4: 00000000001406e0
DR0: 00000000200001c0 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
timerqueue_del+0xd8/0x150 lib/timerqueue.c:83
__remove_hrtimer+0xa8/0x1b0 kernel/time/hrtimer.c:984
remove_hrtimer kernel/time/hrtimer.c:1023 [inline]
hrtimer_try_to_cancel+0x2b8/0x670 kernel/time/hrtimer.c:1150
hrtimer_cancel+0x20/0x40 kernel/time/hrtimer.c:1170
tick_nohz_restart kernel/time/tick-sched.c:625 [inline]
tick_nohz_restart_sched_tick kernel/time/tick-sched.c:841 [inline]
__tick_nohz_idle_restart_tick+0xe5/0x3c0 kernel/time/tick-sched.c:1115
tick_nohz_idle_exit+0x21f/0x290 kernel/time/tick-sched.c:1156
do_idle+0x167/0x570 kernel/sched/idle.c:275
cpu_startup_entry+0x10c/0x120 kernel/sched/idle.c:368
start_secondary+0x433/0x5d0 arch/x86/kernel/smpboot.c:265
secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:242
Modules linked in:
Dumping ftrace buffer:
(ftrace buffer empty)
---[ end trace 0097653b69becc82 ]---
RIP: 0010:rb_next+0xd7/0x140 lib/rbtree.c:541
Code: 49 89 dc 4c 89 eb 48 83 e3 fc 48 89 d8 75 c8 48 83 c4 08 5b 41 5c 41
5d 41 5e 5d c3 48 89 d0 48 8d 78 10 48 89 fa 48 c1 ea 03 <80> 3c 1a 00 75
1a 48 8b 50 10 48 85 d2 75 e3 48 83 c4 08 5b 41 5c
RSP: 0018:ffff8801d9af7ae0 EFLAGS: 00010007
RAX: 23b1e8c689c389ff RBX: dffffc0000000000 RCX: ffffffff8792d801
RDX: 04763d18d1387141 RSI: ffffffff8792d890 RDI: 23b1e8c689c38a0f
RBP: ffff8801d9af7b08 R08: ffff8801d9ae8380 R09: fffffbfff156f2e9
R10: fffffbfff156f2e9 R11: ffffffff8ab7974b R12: ffff8801daf26560
R13: ffff8801ca0878c1 R14: dffffc0000000000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f80ca03ddb8 CR3: 00000001a2003000 CR4: 00000000001406e0
DR0: 00000000200001c0 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

[Dmitry Vyukov]

#syz fix: bpf: sockhash, disallow bpf_tcp_close and update in parallel

> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/0000000000000305720571385b27%40google.com.
> For more options, visit https://groups.google.com/d/optout.