From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: syzbot <syzbot+3f84280d52be9b7083cc@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, dan.j.williams@intel.com,
jglisse@redhat.com, kirill.shutemov@linux.intel.com,
ldufour@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@suse.com, minchan@kernel.org,
ross.zwisler@linux.intel.com, syzkaller-bugs@googlegroups.com,
willy@infradead.org, ying.huang@intel.com
Subject: Re: kernel BUG at mm/memory.c:LINE!
Date: Mon, 9 Jul 2018 13:15:58 +0300 [thread overview]
Message-ID: <20180709101558.63vkwppwcgzcv3dg@kshutemo-mobl1> (raw)
In-Reply-To: <0000000000004a7da505708a9915@google.com>
On Sun, Jul 08, 2018 at 10:51:03PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: b2d44d145d2a Merge tag '4.18-rc3-smb3fixes' of git://git.s..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11d07748400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2ca6c7a31d407f86
> dashboard link: https://syzkaller.appspot.com/bug?extid=3f84280d52be9b7083cc
> compiler: gcc (GCC) 8.0.1 20180413 (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+3f84280d52be9b7083cc@syzkaller.appspotmail.com
>
> next ffff8801ce5e7040 prev ffff8801d20eca50 mm ffff88019c1e13c0
> prot 27 anon_vma ffff88019680cdd8 vm_ops 0000000000000000
> pgoff 0 file ffff8801b2ec2d00 private_data 0000000000000000
> flags: 0xff(read|write|exec|shared|mayread|maywrite|mayexec|mayshare)
> ------------[ cut here ]------------
> kernel BUG at mm/memory.c:1422!
Looks like vma_is_anonymous() false-positive.
Any clues what file is it? I would guess some kind of socket, but it's not
clear from log which exactly.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2018-07-09 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 5:51 syzbot
2018-07-09 10:15 ` Kirill A. Shutemov [this message]
2018-07-09 10:48 ` Dmitry Vyukov
2018-07-09 10:52 ` Dmitry Vyukov
2018-07-09 14:21 ` Kirill A. Shutemov
2018-07-09 15:25 ` Kirill A. Shutemov
2018-07-09 17:23 ` Dmitry Vyukov
2018-07-09 22:07 ` Kirill A. Shutemov
2018-07-10 10:02 ` 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=20180709101558.63vkwppwcgzcv3dg@kshutemo-mobl1 \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jglisse@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=syzbot+3f84280d52be9b7083cc@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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