From: Christopher Li <sparse@chrisli.org>
To: linux-sparse@vger.kernel.org
Cc: Josh Triplett <josh@freedesktop.org>
Subject: Re: [PATCH 5] Adding the NULL pointer checker.
Date: Tue, 16 Jan 2007 18:41:30 -0800 [thread overview]
Message-ID: <20070117024130.GH962@chrisli.org> (raw)
In-Reply-To: <20070117023918.GF962@chrisli.org>
Oops, this should be [PATCH 6] instead.
Chris
On Tue, Jan 16, 2007 at 06:39:18PM -0800, Christopher Li wrote:
>
> Changelog:
> - Using pseudo user list to find out the calling function.
> It doesn't scan instruction one by one any more.
>
> This patch add the kmalloc null pointer checking. It also
> try to track the double free as well. It knows a few kmalloc like
> functions and kfree etc.
>
> The interrupt checking is just a toy. Without cross function checking,
> it is way too many false positive.
>
> Signed-off-by: Christopher Li<sparse@chrisli.org>
>
next prev parent reply other threads:[~2007-01-17 3:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 2:39 [PATCH 5] Adding the NULL pointer checker Christopher Li
2007-01-17 2:41 ` Christopher Li [this message]
2007-01-27 8:20 ` Josh Triplett
2007-01-29 22:30 ` Chris Li
2007-01-29 22:48 ` Linus Torvalds
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=20070117024130.GH962@chrisli.org \
--to=sparse@chrisli.org \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).