From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+aaa6fa4949cc5d9b7b25@syzkaller.appspotmail.com>,
Ingo Molnar <mingo@kernel.org>, Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: BUG: MAX_LOCKDEP_CHAINS too low!
Date: Fri, 28 Sep 2018 09:00:42 +0200 [thread overview]
Message-ID: <20180928070042.GF3439@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CACT4Y+b3AmVQMjPNsPHOXRZS4tNYb6Z9h5-c=1ZwZk0VR-5J5Q@mail.gmail.com>
On Fri, Sep 28, 2018 at 08:06:26AM +0200, Dmitry Vyukov wrote:
> On Fri, Sep 28, 2018 at 7:51 AM, syzbot
> <syzbot+aaa6fa4949cc5d9b7b25@syzkaller.appspotmail.com> wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: c307aaf3eb47 Merge tag 'iommu-fixes-v4.19-rc5' of git://gi..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=13810df1400000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=dfb440e26f0a6f6f
> > dashboard link: https://syzkaller.appspot.com/bug?extid=aaa6fa4949cc5d9b7b25
> > compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> >
> > Unfortunately, I don't have any reproducer for this crash yet.
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+aaa6fa4949cc5d9b7b25@syzkaller.appspotmail.com
>
> +LOCKDEP maintainers,
>
> What does this BUG mean? And how should it be fixed?
>
> Thanks
>
> > BUG: MAX_LOCKDEP_CHAINS too low!
Is the his result of endlessly loading and unloading modules?
In which case, the fix is: don't do that then.
next prev parent reply other threads:[~2018-09-28 7:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 5:51 BUG: MAX_LOCKDEP_CHAINS too low! syzbot
2018-09-28 6:06 ` Dmitry Vyukov
2018-09-28 7:00 ` Peter Zijlstra [this message]
2018-09-28 7:56 ` Dmitry Vyukov
2020-01-09 10:59 ` Dmitry Vyukov
2020-01-13 11:11 ` Dmitry Vyukov
2020-01-15 21:53 ` Cong Wang
2020-01-16 5:25 ` Dmitry Vyukov
2020-01-16 15:32 ` Taehee Yoo
2020-01-16 17:05 ` Dmitry Vyukov
2020-01-16 15:09 ` Taehee Yoo
2020-01-18 20:41 ` Cong Wang
2020-03-04 8:03 ` Dmitry Vyukov
2020-03-04 23:19 ` Cong Wang
2020-01-14 8:43 ` Peter Zijlstra
2020-01-14 10:18 ` Dmitry Vyukov
2019-10-20 23:33 ` syzbot
2020-04-15 18:52 ` Cong Wang
2020-04-15 19:17 ` 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=20180928070042.GF3439@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=syzbot+aaa6fa4949cc5d9b7b25@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.