All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
	torvalds@transmeta.com
Subject: Re: calling schedule() from interupt context
Date: Mon, 25 Nov 2002 08:42:15 +1100	[thread overview]
Message-ID: <20021124223234.7C5EB2C111@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 22 Nov 2002 01:09:34 -0800." <20021122.010934.126934922.davem@redhat.com>

In message <20021122.010934.126934922.davem@redhat.com> you write:
>    From: "dan carpenter" <error27@email.com>
>    Date: Fri, 22 Nov 2002 03:54:41 -0500
> 
>    module_put ==> put_cpu ==> preempt_schedule ==> schedule
> 
> Oh we can't kill module references from interrupts?

Err, no, that would be insane.  get_cpu() & put_cpu() should work
perfectly fine inside interrupts, no?

> Egads... that makes lots of the networking stuff
> nearly impossible as SKB's hold references to modules
> and thus skb freeing can thus put modules.

Relax: modular networking was one of my aims 8)

Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  parent reply	other threads:[~2002-11-24 22:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22  8:54 calling schedule() from interupt context dan carpenter
2002-11-22  9:09 ` David S. Miller
2002-11-22  9:16   ` Robert Love
2002-11-24 21:42   ` Rusty Russell [this message]
2002-11-24 22:41     ` Robert Love
2002-11-22  9:14 ` Robert Love
  -- strict thread matches above, loose matches on Subject: below --
2002-11-22 16:04 dan carpenter
2002-11-22 16:11 ` 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=20021124223234.7C5EB2C111@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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.