From: Aleksandr Nogikh <nogikh@google.com>
To: Sven Eckelmann <sven@narfation.org>
Cc: 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:31:35 +0100 [thread overview]
Message-ID: <CANp29Y7SuK8P8xHa6JzAzs_NxPUN9AvFTiKfMhgLy1POGBodwA@mail.gmail.com> (raw)
In-Reply-To: <2615678.iZASKD2KPV@ripper>
Hi Sven,
On Tue, Mar 19, 2024 at 2:19 PM Sven Eckelmann <sven@narfation.org> wrote:
>
> On Tuesday, 19 March 2024 11:33:17 CET syzbot wrote:
> > syzbot has found a reproducer for the following issue on:
> >
< ... >
>
> 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.
Syzbot looks at several crash reports to determine the bug subsystems
and in this case one of those crashes was pointing to
net/batman-adv/multicast.c:
https://syzkaller.appspot.com/text?tag=CrashReport&x=15afccb3280000
--
Aleksandr
>
> Kind regards,
> Sven
>
> --
prev parent reply other threads:[~2024-03-19 13:31 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
2024-03-19 13:31 ` Aleksandr Nogikh [this message]
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=CANp29Y7SuK8P8xHa6JzAzs_NxPUN9AvFTiKfMhgLy1POGBodwA@mail.gmail.com \
--to=nogikh@google.com \
--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=sven@narfation.org \
--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 NNTP newsgroup(s).