From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+0985c7ea18137bf0c4ca@syzkaller.appspotmail.com>
Cc: hannes@cmpxchg.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, schatzberg.dan@gmail.com,
sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: WARNING in alloc_page_buffers
Date: Sat, 21 Mar 2020 13:07:16 -0700 [thread overview]
Message-ID: <20200321130716.c1da54e6e5b9897ae5dfde38@linux-foundation.org> (raw)
In-Reply-To: <000000000000f0373505a162d972@google.com>
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?
> 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.
next prev parent reply other threads:[~2020-03-21 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 20:00 syzbot
2020-03-21 20:07 ` Andrew Morton [this message]
2020-03-21 20:17 ` 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=20200321130716.c1da54e6e5b9897ae5dfde38@linux-foundation.org \
--to=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
all inboxes | Powered by JetHome®