From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+cea928fd1f13d3cbeee3@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: executor-detected bug
Date: Wed, 30 Jan 2019 19:53:28 +0900 [thread overview]
Message-ID: <dc8bb665-c30f-be49-0592-6b6560a3e9a4@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <000000000000419244058088e841@google.com>
On 2019/01/29 3:33, syzbot wrote:
> 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
This error message was triggered by
doexit(kErrorStatus);
in executor/executor.cc . This is not a kernel bug.
#syz invalid
prev parent reply other threads:[~2019-01-30 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 18:33 BUG: executor-detected bug syzbot
2019-01-30 10:53 ` Tetsuo Handa [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=dc8bb665-c30f-be49-0592-6b6560a3e9a4@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+cea928fd1f13d3cbeee3@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).