From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 7B532405 for ; Sat, 1 Aug 2015 15:26:23 +0000 (UTC) Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1FCDC16B for ; Sat, 1 Aug 2015 15:26:23 +0000 (UTC) Message-ID: <55BCE519.1040207@oracle.com> Date: Sat, 01 Aug 2015 11:26:17 -0400 From: Sasha Levin MIME-Version: 1.0 To: Dan Carpenter References: <55BAE39F.9060705@oracle.com> <55BBB514.7060509@oracle.com> <20150801134546.GO5180@mwanda> In-Reply-To: <20150801134546.GO5180@mwanda> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "ksummit-discuss@lists.linuxfoundation.org" , Dave Jones Subject: Re: [Ksummit-discuss] Self nomination List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 08/01/2015 09:45 AM, Dan Carpenter wrote: > On Fri, Jul 31, 2015 at 01:49:08PM -0400, Sasha Levin wrote: >> - Encouraging folks who add new sysctls (or features to existing sysctls) to contribute >> testing code to the various testing projects around (trinity and such). > > Which other fuzzers are people using besides trinity? I'm not sure, I think trinity sort of took over :) My point was that people should be submitting a more significant amount of test code along with their new ABI - none of the recent syscalls added has any mention in LTP for example. > Also why don't we merge trinity under tools/testing/? I bet people > would keep it in sync better if we did that. No objections on my end. I believe that Dave previously objected because it's hard to make it work on sync with the kernel's release cycle. I've actually presented a proposal in linuxcon back in 2013 for unifying trinity into the kernel, and using common headers for syscalls. This would force people who add/modify syscalls to update trinity, and it'll also make the ABI self documenting as one would need to be very specific about what parameters are expected for each syscall. Thanks, Sasha