From: Joseph Myers <joseph@codesourcery.com>
To: "Zhangjian (Bamvor)" <bamvor.zhangjian@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
libc-alpha@sourceware.org, trinity@vger.kernel.org,
syzkaller@googlegroups.com, aponomarenko@rosalab.ru,
Jess Hertz <jesse.hertz@nccgroup.trust>,
Tim Newsham <tim.newsham@nccgroup.trust>,
arnd@arndb.dea, catalin.marinas@arm.com, broonie@kernel.org,
maxim.kuvyrkov@linaro.org, ynorov@caviumnetworks.com,
pinskia@gmail.com, schwab@suse.de, agraf@suse.de,
marcus.shawcroft@arm.com, dingtianhong@huawei.com,
guohanjun@huawei.com, cuibixuan@huawei.com, lijinyue@huawei.com,
lizefan@huawei.com
Subject: Re: [RFD] Efficient unit test and fuzz tools for kernel/libc porting
Date: Wed, 20 Jul 2016 15:47:35 +0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1607201544220.12251@digraph.polyomino.org.uk> (raw)
In-Reply-To: <577CB5B7.7040204@huawei.com>
On Wed, 6 Jul 2016, Zhangjian (Bamvor) wrote:
> correct or not. After learn and compare some fuzz tools, I feel that there is
> no such fuzz tools could help me. So, I wrote a new fuzz tools base on the
> trinity and it found several wrapper issues in glibc. I will first explain the
> different with existing fuzz tools and paste my propsosal in the end.
I'm not at all clear on whether any of the people working on AArch64 ILP32
glibc have run the glibc testsuite and investigated the results in detail
(the patch submissions have failed to include glibc testsuite results and
have included bugs that would have been detected by the glibc testsuite).
But, if you've found bugs in a new glibc port that were not detected by
the existing testsuite, then tests for those bugs should be contributed to
glibc (even if no existing port has those bugs, improving the test
coverage is still a good idea).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-07-20 15:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 7:39 [RFD] Efficient unit test and fuzz tools for kernel/libc porting Zhangjian (Bamvor)
2016-07-06 7:39 ` Zhangjian (Bamvor)
2016-07-06 8:00 ` Dmitry Vyukov
2016-07-06 8:00 ` Dmitry Vyukov
2016-07-06 8:24 ` Zhangjian (Bamvor)
2016-07-06 8:24 ` Zhangjian (Bamvor)
2016-07-06 9:09 ` Dmitry Vyukov
2016-07-06 10:38 ` Zhangjian (Bamvor)
2016-07-06 10:38 ` Zhangjian (Bamvor)
2016-07-06 8:00 ` Zhangjian (Bamvor)
2016-07-06 8:00 ` Zhangjian (Bamvor)
2016-07-20 15:47 ` Joseph Myers [this message]
2016-07-20 15:47 ` Joseph Myers
2016-07-21 12:39 ` Zhangjian (Bamvor)
2016-07-21 12:39 ` Zhangjian (Bamvor)
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=alpine.DEB.2.20.1607201544220.12251@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=agraf@suse.de \
--cc=aponomarenko@rosalab.ru \
--cc=arnd@arndb.dea \
--cc=bamvor.zhangjian@huawei.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cuibixuan@huawei.com \
--cc=dingtianhong@huawei.com \
--cc=guohanjun@huawei.com \
--cc=jesse.hertz@nccgroup.trust \
--cc=libc-alpha@sourceware.org \
--cc=lijinyue@huawei.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=marcus.shawcroft@arm.com \
--cc=maxim.kuvyrkov@linaro.org \
--cc=pinskia@gmail.com \
--cc=schwab@suse.de \
--cc=syzkaller@googlegroups.com \
--cc=tim.newsham@nccgroup.trust \
--cc=trinity@vger.kernel.org \
--cc=ynorov@caviumnetworks.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