From: Russell King <rmk@arm.linux.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>,
shemminger@osdl.org, davem@redhat.com, netdev@oss.sgi.com,
Greg KH <greg@kroah.com>
Subject: Re: [Fwd: pcmcia ether drivers can't be unloaded]
Date: Tue, 27 Jul 2004 23:36:14 +0100 [thread overview]
Message-ID: <20040727233614.B30782@flint.arm.linux.org.uk> (raw)
In-Reply-To: <41068BEF.7010200@pobox.com>; from jgarzik@pobox.com on Tue, Jul 27, 2004 at 01:07:59PM -0400
On Tue, Jul 27, 2004 at 01:07:59PM -0400, Jeff Garzik wrote:
> It looks like pcmica modular ether (example orinoco) can never be manually
> unloaded because module refcount is always 1. This comes from the owner
> field in the pcmcia_driver.owner being set.
Intended behaviour. As long as the driver is bound to a socket, there are
references to the driver, so we need to keep the refcount non-zero.
Once the driver is unbound (by ejecting cards) then the ref count will
drop to zero and the module can be unloaded.
> One fix is to not set owner field but then there is a hot plug/module
> remove race. But the right fix seems to fix up pcmcia to be a true bus
> in the driver model and have the same hotplug as other buses; usb and
> pci don't have the problem.
No, the right fix is not to try to fsck with PCMCIA refcounting - it
isn't up to having drivers randomly unloaded. IOW, it remains 2.4
behaviour.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next parent reply other threads:[~2004-07-27 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41068BEF.7010200@pobox.com>
2004-07-27 22:36 ` Russell King [this message]
2004-07-28 0:19 ` [Fwd: pcmcia ether drivers can't be unloaded] David S. Miller
2004-07-28 15:50 ` Russell King
2004-07-28 15:54 ` David S. Miller
2004-08-02 19:02 ` Russell King
2004-08-07 11:09 ` Russell King
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=20040727233614.B30782@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=davem@redhat.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).