From: Bart Van Assche <bvanassche@acm.org>
To: syzbot <syzbot+6f39a9deb697359fe520@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, danitg@mellanox.com,
darrick.wong@oracle.com, dledford@redhat.com,
gustavo@embeddedor.com, jannh@google.com, jgg@ziepe.ca,
johannes.berg@intel.com, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-xfs@vger.kernel.org, longman@redhat.com, mingo@kernel.org,
paulmck@linux.vnet.ibm.com, peterz@infradead.org,
roland@purestorage.com, shamir.rabinovitch@oracle.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tj@kernel.org, torvalds@linux-foundation.org,
will.deacon@arm.com, xiyou.wangcong@gmail.com,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: BUG: MAX_STACK_TRACE_ENTRIES too low! (2)
Date: Sat, 30 Mar 2019 19:17:09 -0700 [thread overview]
Message-ID: <f71aaffa-ecf4-1def-fe50-91f37c677537@acm.org> (raw)
In-Reply-To: <00000000000089a718058556e1d8@google.com>
On 3/30/19 2:58 PM, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 669de8bda87b92ab9a2fc663b3f5743c2ad1ae9f
> Author: Bart Van Assche <bvanassche@acm.org>
> Date: Thu Feb 14 23:00:54 2019 +0000
>
> kernel/workqueue: Use dynamic lockdep keys for workqueues
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17f1bacd200000
> start commit: 0e40da3e Merge tag 'kbuild-fixes-v5.1' of
> git://git.kernel..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=1409bacd200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1009bacd200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=8dcdce25ea72bedf
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=6f39a9deb697359fe520
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e1bacd200000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1120fe0f200000
>
> Reported-by: syzbot+6f39a9deb697359fe520@syzkaller.appspotmail.com
> Fixes: 669de8bda87b ("kernel/workqueue: Use dynamic lockdep keys for
> workqueues")
>
> For information about bisection process see:
> https://goo.gl/tpsmEJ#bisection
Hi Dmitry,
This bisection result doesn't make sense to me. As one can see, the
message "BUG: MAX_STACK_TRACE_ENTRIES too low!" does not occur in the
console output the above console output URL points at.
Bart.
next prev parent reply other threads:[~2019-03-31 2:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 10:42 BUG: MAX_STACK_TRACE_ENTRIES too low! (2) syzbot
2019-03-30 11:10 ` syzbot
2019-03-30 21:58 ` syzbot
2019-03-31 2:17 ` Bart Van Assche [this message]
2019-07-10 5:30 ` Eric Biggers
2019-07-10 14:19 ` Bart Van Assche
2019-07-10 17:00 ` Eric Biggers
2019-07-10 17:21 ` Eric Biggers
2019-07-10 17:46 ` Bart Van Assche
2019-07-10 18:02 ` Eric Biggers
2019-07-10 18:36 ` Bart Van Assche
2019-07-10 18:44 ` Eric Dumazet
2019-07-10 19:09 ` Bart Van Assche
2019-07-10 20:47 ` Eric Dumazet
2019-07-10 21:23 ` Bart Van Assche
2019-07-10 22:09 ` Peter Zijlstra
2019-07-11 18:53 ` Bart Van Assche
2019-07-12 8:55 ` Peter Zijlstra
2019-07-12 23:03 ` Bart Van Assche
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=f71aaffa-ecf4-1def-fe50-91f37c677537@acm.org \
--to=bvanassche@acm.org \
--cc=akpm@linux-foundation.org \
--cc=danitg@mellanox.com \
--cc=darrick.wong@oracle.com \
--cc=dledford@redhat.com \
--cc=dvyukov@google.com \
--cc=gustavo@embeddedor.com \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=johannes.berg@intel.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=roland@purestorage.com \
--cc=shamir.rabinovitch@oracle.com \
--cc=syzbot+6f39a9deb697359fe520@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=xiyou.wangcong@gmail.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).