[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201801152325.FGE87548.tSLMFOVHFJOFQO@I-love.SAKURA.ne.jp>
Date: Mon, 15 Jan 2018 23:25:56 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: dvyukov@...gle.com
Cc: bot+980f5e5fc060c37505bd65abb49a963518b269d9@...kaller.appspotmail.com,
ak@...ux.intel.com, akpm@...ux-foundation.org, jack@...e.cz,
jlayton@...hat.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, mgorman@...hsingularity.net, mingo@...nel.org,
npiggin@...il.com, rgoldwyn@...e.com,
syzkaller-bugs@...glegroups.com, axboe@...nel.dk,
tom.leiming@...il.com, hare@...e.de, osandov@...com, shli@...com
Subject: Re: INFO: task hung in filemap_fault
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.
Powered by blists - more mailing lists