From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+742a9c5d4ab05d343c49@syzkaller.appspotmail.com>
Cc: hughd@google.com, jglisse@redhat.com,
kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, willy@infradead.org
Subject: Re: WARNING in collapse_file
Date: Fri, 25 Oct 2019 14:36:23 -0700 [thread overview]
Message-ID: <20191025143623.3e9b0a916635a45865a11ed3@linux-foundation.org> (raw)
In-Reply-To: <00000000000066214a0595b7ea86@google.com>
On Fri, 25 Oct 2019 01:27:07 -0700 syzbot <syzbot+742a9c5d4ab05d343c49@syzkaller.appspotmail.com> wrote:
> syzbot found the following crash on:
>
> HEAD commit: a6fcdcd9 Add linux-next specific files for 20191021
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=11145ed8e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=32434321999f01e9
> dashboard link: https://syzkaller.appspot.com/bug?extid=742a9c5d4ab05d343c49
> 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+742a9c5d4ab05d343c49@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1080 at mm/khugepaged.c:1643
Yup, thanks, this was addressed in v4:
https://ozlabs.org/~akpm/mmotm/broken-out/mmthp-recheck-each-page-before-collapsing-file-thp-v4.patch
prev parent reply other threads:[~2019-10-25 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 8:27 syzbot
2019-10-25 21:36 ` Andrew Morton [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=20191025143623.3e9b0a916635a45865a11ed3@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songliubraving@fb.com \
--cc=syzbot+742a9c5d4ab05d343c49@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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