Re: [syzbot] Re: [syzbot] [bpf?] possible deadlock in queue_stack_map_push_elem

[syzbot <syzbot+252bc5c744d0bba917e1@syzkaller.appspotmail.com>]

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [bpf?] possible deadlock in queue_stack_map_push_elem
Author: memxor@gmail.com

#syz test: https://github.com/kkdwivedi/linux.git res-lock-next

On Thu, 10 Apr 2025 at 15:08, syzbot
<syzbot+252bc5c744d0bba917e1@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> unregister_netdevice: waiting for DEV to become free
>
> unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
>
>
> Tested on:
>
> commit:         e403941b bpf: Convert ringbuf.c to rqspinlock
> git tree:       https://github.com/kkdwivedi/linux.git res-lock-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1511f74c580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=ea2b297a0891c87e
> dashboard link: https://syzkaller.appspot.com/bug?extid=252bc5c744d0bba917e1
> compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Note: no patches were applied.