From: "dan carpenter" <error27@email.com>
To: rml@tech9.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: calling schedule() from interupt context
Date: Fri, 22 Nov 2002 11:04:09 -0500 [thread overview]
Message-ID: <20021122160409.28049.qmail@email.com> (raw)
From: Robert Love <rml@tech9.net>
> On Fri, 2002-11-22 at 03:54, dan carpenter wrote:
>
> (Next time trim your CC list: none of those poor guys needed this
> email..)
>
trimmed.
> > In drivers/net/tokenring/3c359.c xl_interrupt() calls schedule().
> > The path from xl_interupt to schedule is:
> > xl_rx ==> netif_rx ==>
> > kfree_skb ==> __kfree_skb ==>
> > secpath_put ==> __secpath_destroy ==>
> > xfrm_state_put ==> __xfrm_state_destroy ==> xfrm_put_type ==>
> > module_put ==> put_cpu ==> preempt_schedule ==> schedule
>
> Are you actually seeing this code path or is this just what your script
> is showing you?
>
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.
Thanks for the explanation...
regards,
dan carpenter
--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
One click access to the Top Search Engines
http://www.exactsearchbar.com/mailcom
next reply other threads:[~2002-11-22 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 16:04 dan carpenter [this message]
2002-11-22 16:11 ` Robert Love
-- 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=20021122160409.28049.qmail@email.com \
--to=error27@email.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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
all inboxes | Powered by JetHome®