From: "dan carpenter" <error27@email.com>
To: haveblue@us.ibm.com
Cc: kernel-janitor-discuss@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: lock_kernel check...
Date: Tue, 09 Jul 2002 13:22:05 -0500 [thread overview]
Message-ID: <20020709182205.27952.qmail@email.com> (raw)
----- Original Message -----
From: Dave Hansen <haveblue@us.ibm.com>
Date: Tue, 09 Jul 2002 10:41:01 -0700
To: dan carpenter <error27@email.com>
Subject: Re: lock_kernel check...
> dan carpenter wrote:
> > Smatch.pm is from the smatch.sf.net scripts page. Smatch is a
> > really unfinished code checker that I've been working on. It is
> > based on reading the papers about the Stanford checker.
>
> There was a time when I was thinking about the same thing. It kept
> scaring me the more I thought about it.
>
True. But someone is going to write a checker at some point. It's only a couple days work if you know what you are doing. There doesn't seem to be much advantage in waiting a year or two.
> > Unfortunately, after a night of sleep I realize that my script is
> > broken for 2 reasons. 1) Smatch.pm is meant to track state changes
> > down different code paths. But unfortunately it wasn't doing that
> > in this case; it was just going down the code without taking into
> > consideration any if_stmts etc. I'm extremely embarassed about
> > that. Sorry.
>
> Don't be sorry. The script is smarter than the people who caused the
> errors. (once again, probably me)
>
> > 2) What the Stanford checker does is print an error
> > if one return_stmt is called while the kernel is locked and one is
> > called while the kernel is unlocked. This seems reasonable.
>
> Could you clarify that a bit?
>
If someone made a mistake where they always returned under a kernel_lock() they would find the mistake themselves.
Why would they return under kernel_lock() on error, for example, but not on success? That would be confusing. There would still be some false positives but the number of cases is really small.
regards,
dan carpenter
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
Save up to $160 by signing up for NetZero Platinum Internet service.
http://www.netzero.net/?refcd=N2P0602NEP8
next reply other threads:[~2002-07-09 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 18:22 dan carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 17:27 lock_kernel check dan carpenter
2002-07-09 17:41 ` Dave Hansen
[not found] <20020709081059.17951.qmail@email.com>
2002-07-09 9:08 ` Dave Hansen
2002-07-09 10:31 ` Zwane Mwaikambo
2002-07-09 17:04 ` Dave Hansen
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=20020709182205.27952.qmail@email.com \
--to=error27@email.com \
--cc=haveblue@us.ibm.com \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--cc=linux-kernel@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