From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: syzbot <syzbot+a861f52659ae2596492b@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in mark_lock
Date: Tue, 25 Jun 2019 13:06:09 +0200 [thread overview]
Message-ID: <20190625110609.GA3463@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190625110301.GX3419@hirez.programming.kicks-ass.net>
On Tue, Jun 25, 2019 at 01:03:01PM +0200, Peter Zijlstra wrote:
> On Tue, Jun 25, 2019 at 08:20:56AM +0200, Thomas Gleixner wrote:
> > On Mon, 24 Jun 2019, syzbot wrote:
>
> > > syzbot found the following crash on:
> > >
> > > HEAD commit: dc636f5d Add linux-next specific files for 20190620
> > > git tree: linux-next
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=162b68b1a00000
syzcaller folks; why doesn't the above link include the actual kernel
boot, but only the userspace bits starting at syzcaller start?
I was trying to figure out the setup, but there's not enough information
here.
next prev parent reply other threads:[~2019-06-25 11:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 1:37 WARNING in mark_lock syzbot
2019-06-25 6:20 ` Thomas Gleixner
2019-06-25 7:29 ` [net/bpf] " Eric Biggers
2019-07-01 5:32 ` John Fastabend
2019-07-01 5:51 ` syzbot
2019-07-08 16:21 ` John Fastabend
2019-07-08 22:03 ` syzbot
2019-06-25 11:03 ` Peter Zijlstra
2019-06-25 11:06 ` Peter Zijlstra [this message]
2019-06-25 12:07 ` Dmitry Vyukov
2019-06-25 14:01 ` Peter Zijlstra
2019-06-25 14:10 ` Dmitry Vyukov
2019-06-27 22:03 ` 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=20190625110609.GA3463@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+a861f52659ae2596492b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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