From: syzbot <syzbot+cea928fd1f13d3cbeee3@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: BUG: executor-detected bug
Date: Mon, 28 Jan 2019 10:33:04 -0800 [thread overview]
Message-ID: <000000000000419244058088e841@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 30bac164aca7 Revert "Change mincore() to count "mapped" pa..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11888d5f400000
kernel config: https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
dashboard link: https://syzkaller.appspot.com/bug?extid=cea928fd1f13d3cbeee3
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11be4390c00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+cea928fd1f13d3cbeee3@syzkaller.appspotmail.com
vice hsr_slave_0 left promiscuous mode
2019/01/24 16:52:39 executed programs: 197
2019/01/24 16:52:41 BUG: executor-detected bug:
child errored
loop errored
2019/01/24 16:52:41 result: failed=true hanged=false err=executor 0:
detected kernel bug
child errored
loop errored
2019/01/24 16:52:44 executed programs: 225
2019/01/24 16:52:50 executed programs: 246
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2019-01-28 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 18:33 syzbot [this message]
2019-01-30 10:53 ` Tetsuo Handa
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=000000000000419244058088e841@google.com \
--to=syzbot+cea928fd1f13d3cbeee3@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®