From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: dvyukov@google.com
Cc: bot+980f5e5fc060c37505bd65abb49a963518b269d9@syzkaller.appspotmail.com,
ak@linux.intel.com, akpm@linux-foundation.org, jack@suse.cz,
jlayton@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mgorman@techsingularity.net,
mingo@kernel.org, npiggin@gmail.com, rgoldwyn@suse.com,
syzkaller-bugs@googlegroups.com, axboe@kernel.dk,
tom.leiming@gmail.com, hare@suse.de, osandov@fb.com, shli@fb.com
Subject: Re: INFO: task hung in filemap_fault
Date: Mon, 15 Jan 2018 23:25:56 +0900 [thread overview]
Message-ID: <201801152325.FGE87548.tSLMFOVHFJOFQO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <CACT4Y+Z2d6aV86rj5OYiv5Xw=D9xi=vW7RpdzP2X+vTnUjFqfQ@mail.gmail.com>
Dmitry Vyukov wrote:
> >> I am not completely following. You previously mentioned raw.log, which
> >> is a collection of multiple programs, but now you seem to be talking
> >> about a single reproducer. When syzbot manages to reproduce the bug
> >> only with syzkaller program but not with a corresponding C program, it
> >> provides only syzkaller program. It such case it can sense to convert.
> >> But the case you pointed to actually contains C program. So there is
> >> no need to do the conversion at all... What am I missing?
> >>
> >
> > raw.log is not readable for me.
> > I want to see C program even if syzbot did not manage to reproduce the bug.
> > If C program is available, everyone can try reproducing the bug with manually
> > trimmed C program.
>
> If it did not manage to reproduce the bug, there is no C program.
> There is no program at all.
>
What!? Then, what does raw.log contain? I want to read raw.log as C program.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-15 14:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 8:43 syzbot
2017-12-18 14:52 ` Tetsuo Handa
2017-12-18 22:19 ` Tetsuo Handa
2017-12-28 14:09 ` Dmitry Vyukov
2018-01-01 15:27 ` Tetsuo Handa
2018-01-08 9:08 ` Dmitry Vyukov
2018-01-08 10:48 ` Tetsuo Handa
2018-01-15 9:40 ` Dmitry Vyukov
2018-01-15 10:44 ` Tetsuo Handa
2018-01-15 12:29 ` Dmitry Vyukov
2018-01-15 13:43 ` Dmitry Vyukov
2018-01-15 13:56 ` Tetsuo Handa
2018-01-15 14:00 ` Dmitry Vyukov
2018-01-15 14:25 ` Tetsuo Handa [this message]
2018-01-15 14:27 ` Dmitry Vyukov
2018-01-15 14:38 ` Tetsuo Handa
2018-01-08 9:17 ` 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=201801152325.FGE87548.tSLMFOVHFJOFQO@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bot+980f5e5fc060c37505bd65abb49a963518b269d9@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=hare@suse.de \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=osandov@fb.com \
--cc=rgoldwyn@suse.com \
--cc=shli@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom.leiming@gmail.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