LKML Archive on
help / color / mirror / Atom feed
From: Al Viro <>
To: Christopher Li <>
Cc: Andi Kleen <>,,
	linux kernel mail list <>,
	Josh Triplett <>
Subject: Re: [ANNOUNCE] sparse-0.2-cl2 is now available
Date: Sun, 11 Feb 2007 05:50:15 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Feb 10, 2007 at 09:17:58PM -0800, Christopher Li wrote:
> e.g. sparse has not way to know some function only get called with interrupt
> disabled (or some lock already hold). So it assume interrupt is still
> enable and generate wrong warnings. Another example is that some helper
> function will wrap the locking function. Complain about the exit with locking
> hold is wrong.
> I am hoping adding the cross function checking will reduce those false positive.
> Any way, it need more information to reduce false positive.
> I am still working on the cross function checking. May be it will become
> more useful one day.

I have some stuff in that direction, but it take some resurrecting...

  reply	other threads:[~2007-02-11  5:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2007-02-10  0:00 ` Christopher Li
2007-02-10 17:33   ` Andi Kleen
2007-02-11  5:17     ` Christopher Li
2007-02-11  5:50       ` Al Viro [this message]
2007-02-11  6:02         ` Christopher Li
2007-02-11 10:41           ` Andi Kleen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: [ANNOUNCE] sparse-0.2-cl2 is now available' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).