[lkml]   [2016]   [Jul]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFD] Efficient unit test and fuzz tools for kernel/libc porting
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

 \ /
  Last update: 2016-07-20 18:21    [W:0.058 / U:4.236 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site