KASAN: stack-out-of-bounds Read in rb_erase (2)

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 6fcf9b1d4d6c r8169: fix runtime suspend
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=163fb748400000
kernel config: https://syzkaller.appspot.com/x/.config?x=d264f2b04177ca7c
dashboard link: https://syzkaller.appspot.com/bug?extid=8613d1d74f171d99324f
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: []

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+8613d1...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: stack-out-of-bounds in __rb_change_child
include/linux/rbtree_augmented.h:139 [inline]
BUG: KASAN: stack-out-of-bounds in __rb_erase_augmented
include/linux/rbtree_augmented.h:186 [inline]
BUG: KASAN: stack-out-of-bounds in rb_erase+0x34bf/0x3550 lib/rbtree.c:459
Read of size 8 at addr ffff88019cf37728 by task syz-executor5/21751
PANIC: double fault, error_code: 0x0

CPU: 1 PID: 21807 Comm: syz-executor3 Not tainted 4.18.0-rc3+ #47
CPU: 0 PID: 21751 Comm: syz-executor5 Not tainted 4.18.0-rc3+ #47
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__lock_acquire+0x2e/0x5020 kernel/locking/lockdep.c:3294
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Code:
Call Trace:
41
<IRQ>
57 41
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
89 cf
41 56
41
55
49 89
print_address_description+0x6c/0x20b mm/kasan/report.c:256
fd 41
54 45
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.7+0x242/0x2fe mm/kasan/report.c:412
89 cc
__asan_report_load8_noabort+0x14/0x20 mm/kasan/report.c:433
53
__rb_change_child include/linux/rbtree_augmented.h:139 [inline]
__rb_erase_augmented include/linux/rbtree_augmented.h:186 [inline]
rb_erase+0x34bf/0x3550 lib/rbtree.c:459
65 4c
8b 34
25 40
ee 01
00 48
83 e4 f0
48 81
ec 60
03 00
00 48
8b 45
10 <89>
94
24 80
00 00
00 48
ba 00
00
00 00
00 fc ff df
48 89
84 24
98
RSP: 0018:ffff88019ba80f70 EFLAGS: 00010082
RAX: 0000000000000000 RBX: 1ffff1003375026b RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff88f92620
RBP: ffff88019ba81300 R08: 0000000000000000 R09: 0000000000000000
R10: ffff88019d1771b8 R11: ffff8801daf236b3 R12: 0000000000000000
R13: ffffffff88f92620 R14: ffff8801a8d90300 R15: 0000000000000002
FS: 00007f7898f9f700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88019ba80f68 CR3: 00000001b9825000 CR4: 00000000001406e0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:


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

The bpf map bug which leads to random stack crashes (KASAN:
stack-out-of-bounds Read in timerqueue_add). Too many of them so

#syz invalid

> --
> 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/000000000000d7d96605705c5420%40google.com.
> For more options, visit https://groups.google.com/d/optout.