From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Andi Kleen <ak@suse.de>
Cc: "Hen, Shmulik" <shmulik.hen@intel.com>,
"'LKML'" <linux-kernel@vger.kernel.org>,
"'LNML'" <linux-net@vger.kernel.org>
Subject: Re: Locking Between User Context and Soft IRQs in 2.4.0
Date: Sat, 04 Nov 2000 12:07:34 -0500 [thread overview]
Message-ID: <3A044256.D8CD063C@mandrakesoft.com> (raw)
In-Reply-To: <07E6E3B8C072D211AC4100A0C9C5758302B27077@hasmsx52.iil.intel.com> <3A03DABD.AF4B9AD5@mandrakesoft.com> <20001104111909.A11500@gruyere.muc.suse.de> <3A042D04.5B3A7946@mandrakesoft.com> <20001104175659.A15475@gruyere.muc.suse.de>
Andi Kleen wrote:
> All the MOD_INC/DEC_USE_COUNT are done inside the modules themselves. There
> is nothing that would a driver prevent from being unloaded on a different
> CPU while it is already executing in ->open but has not yet executed the add
> yet or after it has executed the _DEC but it is still running in module code
> Normally the windows are pretty small, but very long running interrupt
> on one CPU hitting exactly in the wrong moment can change that.
Module unload calls unregister_netdev, which grabs rtnl_lock.
dev->open runs under rtnl_lock.
Given this, how can the driver be unloaded if dev->open is running?
--
Jeff Garzik | Dinner is ready when
Building 1024 | the smoke alarm goes off.
MandrakeSoft | -/usr/games/fortune
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-04 17:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 14:10 Locking Between User Context and Soft IRQs in 2.4.0 Hen, Shmulik
2000-11-04 9:45 ` Jeff Garzik
2000-11-04 10:19 ` Andi Kleen
2000-11-04 15:36 ` Jeff Garzik
2000-11-04 16:56 ` Andi Kleen
2000-11-04 17:07 ` Jeff Garzik [this message]
2000-11-05 0:38 ` Andi Kleen
2000-11-05 1:28 ` Andrew Morton
2000-11-05 1:52 ` Andrew Morton
2000-11-05 2:32 ` Andi Kleen
2000-11-05 3:39 ` Keith Owens
2000-11-05 3:47 ` Keith Owens
2000-11-05 11:45 ` Andrew Morton
2000-11-06 2:20 ` Paul Gortmaker
2000-11-06 9:55 ` Andrew Morton
2000-11-06 10:05 ` Jeff Garzik
2000-11-06 12:37 ` Keith Owens
2000-11-06 12:49 ` Jeff Garzik
2000-11-06 12:58 ` Keith Owens
2000-11-06 13:09 ` Jeff Garzik
2000-11-06 13:18 ` Keith Owens
2000-11-07 2:23 ` Rusty Russell
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=3A044256.D8CD063C@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=shmulik.hen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox