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 12:27:23 -0500 [thread overview]
Message-ID: <20020709172723.18529.qmail@email.com> (raw)
----- Original Message -----
From: Dave Hansen <haveblue@us.ibm.com>
Date: Tue, 09 Jul 2002 02:08:18 -0700
To: dan carpenter <error27@email.com>
Subject: Re: lock_kernel check...
> cc'ing LKML 'cause this is interesting...
>
> dan carpenter wrote:
> > As you can see, the attached script is dead simple. It prints an
> > error every time you call return while lock_kernel is held. On
> > your computer you will want to comment out print_url() and
> > uncomment the regular print statement.
>
> I am continually amazed at all the simple, useful, cool stuff that
> people come up with. I like!
>
Glad you liked it. :)
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.
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.
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.
I will fix both mistakes later on this week. Unfortunately I'm in the process of moving and looking for a job etc so I might not get to it for a bit.
regards,
dan carpenter
PS. If you liked this script, try out my kmalloc script. I don't think anyone besides me has successfully installed it yet, so if you have any questions I'd be glad to help. :P My phone number until tomorrow evening is (510) 835-7695.
--
__________________________________________________________
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 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 17:27 dan carpenter [this message]
2002-07-09 17:41 ` lock_kernel check Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 18:22 dan carpenter
[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=20020709172723.18529.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