From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+62ebe501c1ce9a91f68c@syzkaller.appspotmail.com>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Alexei Starovoitov <ast@kernel.org>, bpf <bpf@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
David Ahern <dsahern@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
hawk@kernel.org, Ido Schimmel <idosch@mellanox.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Jiri Pirko <jiri@mellanox.com>,
Johannes Berg <johannes.berg@intel.com>,
John Fastabend <john.fastabend@gmail.com>,
Martin KaFai Lau <kafai@fb.com>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
LKML <linux-kernel@vger.kernel.org>,
Michal Kubecek <mkubecek@suse.cz>,
netdev <netdev@vger.kernel.org>,
petrm@mellanox.com, Roopa Prabhu <roopa@cumulusnetworks.com>,
Song Liu <songliubraving@fb.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Yonghong Song <yhs@fb.com>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Boqun Feng <boqun.feng@gmail.com>
Subject: Re: WARNING in print_bfs_bug
Date: Mon, 28 Sep 2020 09:56:12 +0200 [thread overview]
Message-ID: <20200928075612.GB2594@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CACT4Y+YBi=5Q0tpND7FKU1j1YNy1Pe+Xkgc+c_Xtf_L_pyAcqg@mail.gmail.com>
On Sun, Sep 27, 2020 at 10:57:24AM +0200, Dmitry Vyukov wrote:
> On Thu, Oct 31, 2019 at 9:39 PM syzbot
> <syzbot+62ebe501c1ce9a91f68c@syzkaller.appspotmail.com> wrote:
> >
> > syzbot has found a reproducer for the following crash on:
> >
> > HEAD commit: 49afce6d Add linux-next specific files for 20191031
> > git tree: linux-next
> > console output: https://syzkaller.appspot.com/x/log.txt?x=11eea36ce00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f119b33031056
> > dashboard link: https://syzkaller.appspot.com/bug?extid=62ebe501c1ce9a91f68c
> > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c162f4e00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=131b5eb8e00000
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+62ebe501c1ce9a91f68c@syzkaller.appspotmail.com
>
> This is another LOCKDEP-related top crasher. syzkaller finds just this
> one (see below).
> I think we need to disable LOCKDEP temporary until this and other
> LOCKDEP issues are resolved. I've filed
> https://github.com/google/syzkaller/issues/2140 to track
> disabling/enabling.
There is a potential patch for it:
https://lkml.kernel.org/r/20200917080210.108095-1-boqun.feng@gmail.com
Let me try and digest it.
next prev parent reply other threads:[~2020-09-28 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 8:36 WARNING in print_bfs_bug syzbot
2019-10-31 20:39 ` syzbot
2020-09-27 8:57 ` Dmitry Vyukov
2020-09-28 7:56 ` Peter Zijlstra [this message]
2019-11-01 1:02 ` syzbot
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=20200928075612.GB2594@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ast@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dvyukov@google.com \
--cc=f.fainelli@gmail.com \
--cc=hawk@kernel.org \
--cc=idosch@mellanox.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=johannes.berg@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=petrm@mellanox.com \
--cc=roopa@cumulusnetworks.com \
--cc=songliubraving@fb.com \
--cc=syzbot+62ebe501c1ce9a91f68c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.org \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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).