From: Dave Jones <davej@redhat.com>
To: "Pádraig Brady" <P@draigBrady.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Simple script that locks up my box with recent kernels
Date: Wed, 22 Nov 2006 12:58:56 -0500 [thread overview]
Message-ID: <20061122175856.GH533@redhat.com> (raw)
In-Reply-To: <45642744.2080109@draigBrady.com>
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
next prev parent reply other threads:[~2006-11-22 17:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 23:36 Simple script that locks up my box with recent kernels Jesper Juhl
2006-10-06 23:54 ` Andrew Morton
2006-10-07 0:06 ` Jesper Juhl
2006-10-07 0:21 ` Jesper Juhl
2006-10-07 3:11 ` Linus Torvalds
2006-10-07 21:02 ` Jesper Juhl
2006-10-07 21:25 ` Linus Torvalds
2006-10-08 23:33 ` Jesper Juhl
2006-10-16 22:45 ` Jesper Juhl
2006-10-16 23:04 ` Linus Torvalds
2006-10-16 23:13 ` Jesper Juhl
2006-10-23 20:30 ` Jesper Juhl
2006-11-22 0:46 ` Jesper Juhl
2006-11-22 2:36 ` Linus Torvalds
2006-11-22 3:25 ` Dave Jones
2006-11-22 3:44 ` Linus Torvalds
2006-11-22 3:49 ` Dave Jones
2006-11-22 10:32 ` Pádraig Brady
2006-11-22 17:58 ` Dave Jones [this message]
2006-11-22 8:03 ` Jens Axboe
2006-11-22 10:55 ` Jesper Juhl
2006-11-22 10:57 ` Jens Axboe
2006-11-22 11:04 ` Jesper Juhl
2006-11-22 11:07 ` Jens Axboe
2006-11-23 23:52 ` Jesper Juhl
2006-11-24 6:52 ` Jens Axboe
2006-11-24 9:41 ` Jesper Juhl
2006-11-24 9:46 ` Jens Axboe
2006-11-24 9:52 ` Jesper Juhl
2006-11-23 10:22 ` Jesper Juhl
2006-11-23 23:48 ` Jesper Juhl
2006-11-22 11:00 ` Jesper Juhl
2006-11-24 0:50 ` Jesper Juhl
2006-10-07 3:40 ` Grant Coady
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=20061122175856.GH533@redhat.com \
--to=davej@redhat.com \
--cc=P@draigBrady.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.