From: Dmitry Vyukov <dvyukov@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+0985c7ea18137bf0c4ca@syzkaller.appspotmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
schatzberg.dan@gmail.com, Stephen Rothwell <sfr@canb.auug.org.au>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: WARNING in alloc_page_buffers
Date: Sat, 21 Mar 2020 21:17:26 +0100 [thread overview]
Message-ID: <CACT4Y+YNRv_yZTp0b-8rsPEAN4We_P-0Rx+sHvu95mpQUBf57Q@mail.gmail.com> (raw)
In-Reply-To: <20200321130716.c1da54e6e5b9897ae5dfde38@linux-foundation.org>
On Sat, Mar 21, 2020 at 9:07 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Sat, 21 Mar 2020 13:00:18 -0700 syzbot <syzbot+0985c7ea18137bf0c4ca@syzkaller.appspotmail.com> wrote:
>
> > syzbot found the following crash on:
> >
> > HEAD commit: 770fbb32 Add linux-next specific files for 20200228
>
> That's nearly four weeks ago?
Yes, syzbot did not get any kernel build that boots on linux-next for
the past 3 weeks at least, it either does not build or does not boot:
https://syzkaller.appspot.com/bug?id=0b5a478272f2f91e39199ea606c13f2bc945ac1e
https://syzkaller.appspot.com/bug?id=738c77b954cc37a5b9749c248b33e5d383a1c949
https://syzkaller.appspot.com/bug?id=d085d2f9d904d7e8f4f6f4ec2762d817f58f448d
https://syzkaller.appspot.com/bug?id=ba5d229611dfff6ce6f7470d7548cd0487292104
https://syzkaller.appspot.com/bug?id=f13120b0dfe367862cd8de7bcca9d43a566e5543
The current breakage was reported more than a week ago. Maybe there
are more breakages piled up before behind that one now...
It tries on every commit now.
> > git tree: linux-next
> > console output: https://syzkaller.appspot.com/x/log.txt?x=13507489e00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=576314276bce4ad5
> > dashboard link: https://syzkaller.appspot.com/bug?extid=0985c7ea18137bf0c4ca
> > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b970e5e00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=178e99f9e00000
> >
> > The bug was bisected to:
> >
> > commit c9e1feb96bd90a4b51d440a015ba2f1c0562de59
> > Author: Dan Schatzberg <schatzberg.dan@gmail.com>
> > Date: Tue Feb 25 04:14:08 2020 +0000
> >
> > loop: charge i/o to mem and blk cg
>
> That commit was dropped on March 3.
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/20200321130716.c1da54e6e5b9897ae5dfde38%40linux-foundation.org.
prev parent reply other threads:[~2020-03-21 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 20:00 WARNING in alloc_page_buffers syzbot
2020-03-21 20:07 ` Andrew Morton
2020-03-21 20:17 ` Dmitry Vyukov [this message]
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=CACT4Y+YNRv_yZTp0b-8rsPEAN4We_P-0Rx+sHvu95mpQUBf57Q@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schatzberg.dan@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+0985c7ea18137bf0c4ca@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).