From: Ferenc Wagner <wferi@niif.hu>
To: David Miller <davem@davemloft.net>
Cc: shemminger@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: network driver usage count
Date: Fri, 23 Nov 2007 11:09:27 +0100 [thread overview]
Message-ID: <87pry1ff3c.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: <20071122.170458.260273849.davem@davemloft.net> (David Miller's message of "Thu, 22 Nov 2007 17:04:58 -0800 (PST)")
David Miller <davem@davemloft.net> writes:
> From: Wagner Ferenc <wferi@niif.hu>
> Date: Wed, 21 Nov 2007 23:16:59 +0100
>
>> Hmm, that would warrant nuking all the reference counts on every
>> driver.
>
> That's not true. When packets are in flight, references go
> to the device and the device cannot be unloaded until those
> references get dropped.
I'm trying to understand it. Do you mean that the "usage count" in
the lsmod output does not express the user's view of a piece of *ware
being in use, but rather the number of internal kernel references to
it, which would become invalid should that piece disappear? Where the
former "invalidily" means some undetectable and uncorrectable
inconsistency in the kernel data structures, which leads to a kernel
crash.
> This behavior makes sense because otherwise you have to figure
> out the myriad of references (each ipv4 address, each ipv6
> address, routes, ARP entries, etc.) just to perform such a
> simple operation.
Yes, that's the user's idea of a network device being in use. It can
get hairy indeed.
> If you do not mean to unload the device, simply do not do it.
Now I know...
--
Thanks for taking the time,
Feri.
prev parent reply other threads:[~2007-11-23 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 19:45 Ferenc Wagner
2007-11-21 21:04 ` Stephen Hemminger
2007-11-21 22:16 ` Wagner Ferenc
2007-11-21 23:53 ` Francois Romieu
2007-11-23 1:04 ` David Miller
2007-11-23 10:09 ` Ferenc Wagner [this message]
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=87pry1ff3c.fsf@tac.ki.iif.hu \
--to=wferi@niif.hu \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@linux-foundation.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
all inboxes | Powered by JetHome®