[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061122175856.GH533@redhat.com>
Date: Wed, 22 Nov 2006 12:58:56 -0500
From: Dave Jones <davej@...hat.com>
To: Pádraig Brady <P@...igBrady.com>
Cc: Linus Torvalds <torvalds@...l.org>,
Jesper Juhl <jesper.juhl@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>
Subject: Re: Simple script that locks up my box with recent kernels
On Wed, Nov 22, 2006 at 10:32:36AM +0000, Pádraig Brady wrote:
> > Heh, it's amazing how commonplace that mistake is.
> > Come back bzero, all is forgiven..
>
> It's interesting to do the following on google codesearch
>
> lang:^(c|c\+\+)$ memset\ *\(.*,\ *0\ *\);
> http://tinyurl.com/y47qu4
>
> lang:^(c|c\+\+)$ \sif\([^)]*\);
> http://tinyurl.com/y4mdbl
>
> It would be interesting to build
> up a suite of these regular expressions.
A bunch of people already started gathering these a day
or so after codesearch launched..
http://asert.arbornetworks.com/2006/10/static-code-analysis-using-google-code-search/
is a good start.
http://www.cipher.org.uk/index.php?p=projects/bugle.project
is also somewhat interesting (but from a security bug standpoint only)
I've got some crufty shell scripts that I grew that I use
from time to time that just grep a bunch of patterns, I've had
"put them all together and make one decent one" on my todo
for a while. I'll see if I can get to it this week.
I've used these occasionally not just to find bugs in the kernel
but across a completely unpacked distro source tree.
Amazing what turns up sometimes.
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists