Stack corruption + bpf maps in repro triggers some bells. +bpf mailing list.
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by:
syzbot+97deee...@syzkaller.appspotmail.com
>
> Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in:
> lock_release+0x866/0x960 kernel/locking/lockdep.c:4435
> CPU: 0 PID: 9965 Comm: syz-executor.0 Not tainted 5.3.0-rc6+ #182
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Call Trace:
> Kernel Offset: disabled
> Rebooting in 86400 seconds..
>
>
> ---
> 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#status for how to communicate with syzbot.
> syzbot can test patches for this bug, for details see:
>
https://goo.gl/tpsmEJ#testing-patches
>
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to