From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/18 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Weekly reports: A Date: Fri, 27 May 2011 22:02:38 -0400 Message-ID: <20110528020238.GZ277@brightrain.aerifal.cx> References: <4DDA9C8E.5020105@gmail.com> <20110524010029.GA11834@openwall.com> <20110524011320.GV277@brightrain.aerifal.cx> <4DE043DA.1020104@gmail.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1306548816 10947 80.91.229.12 (28 May 2011 02:13:36 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 28 May 2011 02:13:36 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-101-gllmg-musl=m.gmane.org@lists.openwall.com Sat May 28 04:13:28 2011 Return-path: Envelope-to: gllmg-musl@lo.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1QQ91r-0001v9-Ho for gllmg-musl@lo.gmane.org; Sat, 28 May 2011 04:13:27 +0200 Original-Received: (qmail 18111 invoked by uid 550); 28 May 2011 02:13:27 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 18103 invoked from network); 28 May 2011 02:13:26 -0000 Content-Disposition: inline In-Reply-To: <4DE043DA.1020104@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:18 Archived-At: On Sat, May 28, 2011 at 02:37:46AM +0200, Luka Marčetić wrote: > On 05/24/2011 03:13 AM, Rich Felker wrote: > >>> For "low and high byte content", I suggest that you include ability to > >>> test all byte values (for non-wide chars). glibc and many other libc's > >>> include implementations of string functions that use adds/bitmasks; > >>> these might contain bugs that only show up with specific byte values in > >>> specific character positions when the libc is built for specific CPUs. > >I agree. I don't believe any such issues affect the current C > >implementations in musl, but it would be nice to have the tests in > >place in case anyone wants to add arch-specific asm versions. > > Hey guys. > I would just like to point out that the above, combined with the > "all alignments" requirement from the wiki means I'm essentially > brute-forcing string.h functions. While I generally dislike the > idea, it's a.. thorough approach.. I guess. As a slight remedy I'll The whole point is to brute force all combinations of input that are expected to make a difference to what paths the code might take. > "brute force" with smaller buffers, and only do basic tests with > huge ones. I hope that won't miss the point then. Will report how Indeed of course you can't brute force all possible sequences of bytes up to several GB. :-) I'll leave coming up with a reasonable evalulation of what's needed and what's not as part of your task. Rich