From: Sean Christopherson <sean.j.christopherson@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: syzbot <syzbot+c92d3646e35bc5d1a909@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, arnd@arndb.de, dave@stgolabs.net,
linux-kernel@vger.kernel.org, linux@dominikbrodowski.net,
manfred@colorfullife.com, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: corrupted list in freeary
Date: Tue, 27 Nov 2018 08:22:45 -0800 [thread overview]
Message-ID: <20181127162244.GC27075@linux.intel.com> (raw)
In-Reply-To: <87d0qqjyg6.fsf@xmission.com>
On Tue, Nov 27, 2018 at 10:07:53AM -0600, Eric W. Biederman wrote:
>
>
> syzbot <syzbot+c92d3646e35bc5d1a909@syzkaller.appspotmail.com> writes:
>
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: e195ca6cb6f2 Merge branch 'for-linus' of git://git.kernel...
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=10d3e6a3400000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=73e2bc0cb6463446
> > dashboard link: https://syzkaller.appspot.com/bug?extid=c92d3646e35bc5d1a909
> > compiler: gcc (GCC) 8.0.1 20180413 (experimental)
>
> I don't have this commit. I don't have a clue where it find this
> commit. I can't possibly look into this let alone debug this.
It's in v4.20-rc4.
>
> That is not a useful but report. Please fix your bot.
>
> Eric
>
>
next prev parent reply other threads:[~2018-11-27 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 15:52 BUG: corrupted list in freeary syzbot
2018-11-27 16:07 ` Eric W. Biederman
2018-11-27 16:22 ` Sean Christopherson [this message]
[not found] ` <621f7c52-de52-eb35-bf61-e839adee7ec9@colorfullife.com>
2018-11-30 17:58 ` Dmitry Vyukov
2018-11-30 18:06 ` Dmitry Vyukov
2018-12-01 20:22 ` Manfred Spraul
2018-12-03 14:53 ` Dmitry Vyukov
2019-03-26 8:47 ` Dmitry Vyukov
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=20181127162244.GC27075@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dave@stgolabs.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=manfred@colorfullife.com \
--cc=syzbot+c92d3646e35bc5d1a909@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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.