From: Eric Biggers <ebiggers@kernel.org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+ce541a23cf58c1f6b1b1@syzkaller.appspotmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
yeyunfeng@huawei.com, Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: linux-next boot error: can't ssh into the instance (3)
Date: Mon, 18 Nov 2019 21:02:19 -0800 [thread overview]
Message-ID: <20191119050219.GJ163020@sol.localdomain> (raw)
In-Reply-To: <CAHp75Vf6hfh0+MxX7G5=skcTx+_37ypz_KMi-NYLGB7wW5zs5g@mail.gmail.com>
On Mon, Nov 18, 2019 at 07:37:27PM +0200, Andy Shevchenko wrote:
> On Mon, Nov 18, 2019 at 7:16 PM Dmitry Vyukov <dvyukov@google.com> wrote:
> >
> > On Mon, Nov 18, 2019 at 5:35 PM syzbot
> > <syzbot+ce541a23cf58c1f6b1b1@syzkaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit: 519ead8f Add linux-next specific files for 20191118
> > > git tree: linux-next
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=14653416e00000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=652dd3906d691711
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=ce541a23cf58c1f6b1b1
> > > compiler: gcc (GCC) 9.0.0 20181231 (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+ce541a23cf58c1f6b1b1@syzkaller.appspotmail.com
> >
> >
> > Looks at the console output, this seems to be related to:
> >
> > commit eb09878e13013f0faee0a97562da557c4026b8a1
> > Author: Yunfeng Ye <yeyunfeng@huawei.com>
> > Date: Thu Nov 14 15:16:24 2019 +0800
> >
> > ACPI: sysfs: Change ACPI_MASKABLE_GPE_MAX to 0x100
> >
> > +drivers/acpi/sysfs.c maintainers
>
> Just bisected to the same
>
I had to revert this in order to boot linux-next as well. Rafael, can this
please be reverted?
Thanks,
- Eric
next prev parent reply other threads:[~2019-11-19 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000ee674f0597a18709@google.com>
2019-11-18 17:11 ` linux-next boot error: can't ssh into the instance (3) Dmitry Vyukov
2019-11-18 17:37 ` Andy Shevchenko
2019-11-19 5:02 ` Eric Biggers [this message]
2019-11-19 8:27 ` Rafael J. Wysocki
2019-11-19 17:42 ` Eric Biggers
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=20191119050219.GJ163020@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=dvyukov@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=syzbot+ce541a23cf58c1f6b1b1@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yeyunfeng@huawei.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