From: Bart Van Assche <bvanassche@acm.org>
To: syzbot <syzbot+78923eea7cf44364f4fb@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, darrick.wong@oracle.com,
dledford@redhat.com, gustavo@embeddedor.com, hch@infradead.org,
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, mingo@redhat.com,
paulmck@linux.vnet.ibm.com, peterz@infradead.org,
roland@purestorage.com, sean.hefty@intel.com,
shamir.rabinovitch@oracle.com, swise@opengridcomputing.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tj@kernel.org, torvalds@linux-foundation.org,
will.deacon@arm.com, xiyou.wangcong@gmail.com
Subject: Re: BUG: MAX_STACK_TRACE_ENTRIES too low!
Date: Mon, 11 Mar 2019 08:19:34 -0700 [thread overview]
Message-ID: <1552317574.45180.94.camel@acm.org> (raw)
In-Reply-To: <00000000000080952b0583d183f0@google.com>
On Mon, 2019-03-11 at 06:26 -0700, 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=17dec757200000
> start commit: 669de8bd kernel/workqueue: Use dynamic lockdep keys for wo..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=143ec757200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=103ec757200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=bd349f14600e1305
> dashboard link: https://syzkaller.appspot.com/bug?extid=78923eea7cf44364f4fb
> userspace arch: amd64
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=149c858d200000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111aee33200000
>
> Reported-by: syzbot+78923eea7cf44364f4fb@syzkaller.appspotmail.com
> Fixes: 669de8bd ("kernel/workqueue: Use dynamic lockdep keys for
> workqueues")
I think this issue has been fixed by a commit that went upstream yesterday. Hence:
#syz fix: workqueue, lockdep: Fix an alloc_workqueue() error path
next prev parent reply other threads:[~2019-03-11 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 7:06 BUG: MAX_STACK_TRACE_ENTRIES too low! syzbot
2019-03-02 11:45 ` syzbot
2019-03-08 8:11 ` Christoph Hellwig
2019-03-11 13:26 ` syzbot
2019-03-11 15:19 ` Bart Van Assche [this message]
2019-03-11 17:48 ` Linus Torvalds
2019-03-11 18:17 ` Bart Van Assche
-- strict thread matches above, loose matches on Subject: below --
2009-02-19 12:37 Geert Uytterhoeven
2009-02-19 13:16 ` Gary Thomas
2008-04-17 22:01 Christian Kujau
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=1552317574.45180.94.camel@acm.org \
--to=bvanassche@acm.org \
--cc=akpm@linux-foundation.org \
--cc=darrick.wong@oracle.com \
--cc=dledford@redhat.com \
--cc=gustavo@embeddedor.com \
--cc=hch@infradead.org \
--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=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=roland@purestorage.com \
--cc=sean.hefty@intel.com \
--cc=shamir.rabinovitch@oracle.com \
--cc=swise@opengridcomputing.com \
--cc=syzbot+78923eea7cf44364f4fb@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