From: Matthew Wilcox <willy@infradead.org>
To: syzbot <syzbot+b8e0dfee3fd8c9012771@syzkaller.appspotmail.com>
Cc: hughd@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: Re: kernel BUG at mm/shmem.c:LINE!
Date: Mon, 9 Jul 2018 07:36:10 -0700 [thread overview]
Message-ID: <20180709143610.GD2662@bombadil.infradead.org> (raw)
In-Reply-To: <000000000000d624c605705e9010@google.com>
On Fri, Jul 06, 2018 at 06:19:02PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 526674536360 Add linux-next specific files for 20180706
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=116d16fc400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c8d1cfc0cb798e48
> dashboard link: https://syzkaller.appspot.com/bug?extid=b8e0dfee3fd8c9012771
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=170e462c400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15f1ba2c400000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+b8e0dfee3fd8c9012771@syzkaller.appspotmail.com
#syz fix: shmem: Convert shmem_add_to_page_cache to XArray
next prev parent reply other threads:[~2018-07-09 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 1:19 kernel BUG at mm/shmem.c:LINE! syzbot
2018-07-07 2:57 ` Matthew Wilcox
2018-07-09 14:36 ` Matthew Wilcox [this message]
2018-07-23 2:28 ` Hugh Dickins
2018-07-23 14:01 ` Matthew Wilcox
2018-07-23 19:14 ` Hugh Dickins
2018-07-23 20:36 ` Matthew Wilcox
2018-07-23 22:42 ` Hugh Dickins
2018-07-23 22:54 ` Matthew Wilcox
2018-07-24 9:12 ` Hugh Dickins
2018-07-26 6:53 ` Hugh Dickins
2018-07-26 14:33 ` Matthew Wilcox
2018-07-26 16:40 ` Hugh Dickins
2018-07-26 19:32 ` Matthew Wilcox
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=20180709143610.GD2662@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+b8e0dfee3fd8c9012771@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 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).