From: "Theodore Ts'o" <tytso@mit.edu>
To: Chen Feng <puck.chen@hisilicon.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
zhaoyukun@huawei.com, arnd@arndb.de,
linux-kernel@vger.kernel.org, suzhuangluan@hisilicon.com,
dan.zhao@hisilicon.com
Subject: Re: [PATCH RFC] random: fix syzkaller fuzzer test int overflow
Date: Thu, 26 Oct 2017 11:04:45 -0400 [thread overview]
Message-ID: <20171026150445.s3rxcy4btlisdu5q@thunk.org> (raw)
In-Reply-To: <59F19BEB.7090100@hisilicon.com>
On Thu, Oct 26, 2017 at 04:25:15PM +0800, Chen Feng wrote:
>
>
> On 2017/10/25 16:49, Theodore Ts'o wrote:
> > Other people who have sent me fuzzer test reproducers are able to
> > reproduce syzkaller logs into a simple C program. Can you explain to
> > me what the heck:
> >
> >> r3 = syz_open_dev$urandom(&(0x7f000000a000)="2f6465762f7572616e646f6d00", 0x0, 0x0)
> >
> > means?
>
> Take a look at this:
>
> https://github.com/google/syzkaller/blob/master/sys/linux/random.txt
Sorry, this *still* looks like gobbledygook.
What ioctls are you executing, and with what arguments?
*Please*, give me a C program I can compile.
-Ted
next prev parent reply other threads:[~2017-10-26 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 7:44 Chen Feng
2017-10-24 9:09 ` Greg KH
2017-10-24 9:24 ` Chen Feng
2017-10-24 9:57 ` Greg KH
2017-10-24 10:25 ` Theodore Ts'o
2017-10-25 6:30 ` Chen Feng
2017-10-25 6:56 ` Greg KH
2017-10-25 7:08 ` Chen Feng
2017-10-25 8:49 ` Theodore Ts'o
2017-10-26 8:25 ` Chen Feng
2017-10-26 15:04 ` Theodore Ts'o [this message]
2017-10-28 3:22 ` Chen Feng
2017-10-29 18:25 ` Theodore Ts'o
2017-10-30 7:39 ` Greg KH
2017-10-30 9:11 ` Theodore Ts'o
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=20171026150445.s3rxcy4btlisdu5q@thunk.org \
--to=tytso@mit.edu \
--cc=arnd@arndb.de \
--cc=dan.zhao@hisilicon.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=puck.chen@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=zhaoyukun@huawei.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
Powered by JetHome