From: Robert Love <rml@tech9.net>
To: dan carpenter <error27@email.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: calling schedule() from interupt context
Date: 22 Nov 2002 11:11:16 -0500 [thread overview]
Message-ID: <1037981475.1504.4316.camel@phantasy> (raw)
In-Reply-To: <20021122160409.28049.qmail@email.com>
On Fri, 2002-11-22 at 11:04, dan carpenter wrote:
> ok. I'm an idiot.
>
> The script only checks things at compile time not at runtime. So you are
> right, of course, that this couldn't happen in real life because of the
> preemp_count.
Still, neat scripts.
Statically searching code has a lot of applications that run-time
checking does not have. For example, there _are_ a lot of things you do
not want to call from interrupts: down(), kmalloc() without GFP_ATOMIC,
etc. etc.
And could you get it to check for code paths that could possibly
double-acquire the same lock?
etc. etc... be creative.
> Thanks for the explanation...
No problem.
Robert Love
next prev parent reply other threads:[~2002-11-22 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 16:04 calling schedule() from interupt context dan carpenter
2002-11-22 16:11 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 8:54 dan carpenter
2002-11-22 9:09 ` David S. Miller
2002-11-22 9:16 ` Robert Love
2002-11-24 21:42 ` Rusty Russell
2002-11-24 22:41 ` Robert Love
2002-11-22 9:14 ` Robert Love
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=1037981475.1504.4316.camel@phantasy \
--to=rml@tech9.net \
--cc=error27@email.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.