From: "Suhabe Bugrara" <suhabe@stanford.edu>
To: linux-sparse@VGER.KERNEL.ORG
Subject: Re: [PATCH 7] Adding the interrupt checker
Date: Fri, 30 Mar 2007 17:26:55 -0700 [thread overview]
Message-ID: <5166c2f30703301726q2a3cfb91p7fdb5f7ae146d22d@mail.gmail.com> (raw)
On Thu, 2007-03-01 at 6:07:06, Pavel Roskin wrote:
> Moreover, I think that incorrect use of locking is a remaining major
> issue not covered by sparse.
Hello,
What particular locking usage rules would Sparse ideally check? I
guess this would include finding double locking/unlocking errors. Are
there other more important locking usage rules? Could locking errors
in the kernel be potentially more serious than dereferencing an
unchecked user pointer for example?
Suhabe
next reply other threads:[~2007-03-31 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 0:26 Suhabe Bugrara [this message]
2007-04-02 16:52 ` [PATCH 7] Adding the interrupt checker Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2007-02-10 0:26 Christopher Li
2007-03-01 6:07 ` Pavel Roskin
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=5166c2f30703301726q2a3cfb91p7fdb5f7ae146d22d@mail.gmail.com \
--to=suhabe@stanford.edu \
--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).