From: Sven Eckelmann <sven@narfation.org>
To: akpm@linux-foundation.org, andrii@kernel.org, ast@kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, bpf@vger.kernel.org,
christian@brauner.io, daniel@iogearbox.net, dvyukov@google.com,
edumazet@google.com, elver@google.com, glider@google.com,
hdanton@sina.com, jakub@cloudflare.com, jannh@google.com,
john.fastabend@gmail.com, kasan-dev@googlegroups.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mareklindner@neomailbox.ch,
mark.rutland@arm.com, netdev@vger.kernel.org, pabeni@redhat.com,
shakeelb@google.com, syzkaller-bugs@googlegroups.com,
syzbot <syzbot+8983d6d4f7df556be565@syzkaller.appspotmail.com>
Subject: Re: [syzbot] [batman?] [bpf?] possible deadlock in lock_timer_base
Date: Tue, 19 Mar 2024 14:19:20 +0100 [thread overview]
Message-ID: <2615678.iZASKD2KPV@ripper> (raw)
In-Reply-To: <000000000000901b1c0614010091@google.com>
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
On Tuesday, 19 March 2024 11:33:17 CET syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 35c3e2791756 Revert "net: Re-use and set mono_delivery_tim..
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=10569181180000
> kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
> dashboard link: https://syzkaller.appspot.com/bug?extid=8983d6d4f7df556be565
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d9fa4e180000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137afac9180000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/26b55a26fc12/disk-35c3e279.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/6f39fa55c828/vmlinux-35c3e279.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/e1e0501539e6/bzImage-35c3e279.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+8983d6d4f7df556be565@syzkaller.appspotmail.com
Sorry, this is a little bit off-topic. But how does sysbot figure out the
subsystems (like "[batman?]"). Because neither the reproducer nor the
backtrace nor the console output mention anything batman-adv related.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-19 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000c0645805b7f982e4@google.com>
2024-03-19 10:33 ` [syzbot] [batman?] [bpf?] possible deadlock in lock_timer_base syzbot
2024-03-19 13:19 ` Sven Eckelmann [this message]
2024-03-19 13:31 ` Aleksandr Nogikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2615678.iZASKD2KPV@ripper \
--to=sven@narfation.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bpf@vger.kernel.org \
--cc=christian@brauner.io \
--cc=daniel@iogearbox.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hdanton@sina.com \
--cc=jakub@cloudflare.com \
--cc=jannh@google.com \
--cc=john.fastabend@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mareklindner@neomailbox.ch \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shakeelb@google.com \
--cc=syzbot+8983d6d4f7df556be565@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).