From: "David S. Miller" <davem@redhat.com>
To: rmk@arm.linux.org.uk
Cc: rol@as2917.net, cfriesen@nortelnetworks.com, paulus@samba.org,
linux-kernel@vger.kernel.org, linux-ppp@vger.kernel.org,
linux-net@vger.kernel.org
Subject: Re: [BUG]: problem when shutting down ppp connection since 2.5.70
Date: Mon, 30 Jun 2003 01:03:37 -0700 (PDT) [thread overview]
Message-ID: <20030630.010337.74723316.davem@redhat.com> (raw)
In-Reply-To: <20030630090507.A32593@flint.arm.linux.org.uk>
From: Russell King <rmk@arm.linux.org.uk>
Date: Mon, 30 Jun 2003 09:05:07 +0100
People with PCMCIA cards have been reporting the same thing. It sounds
like something's up with the netdev layer, and it has persisted until
2.5.73 thus far.
If there are bugs in pcmcia drivers, they are _really_ going to show
now. The change is that 'rmmod' is allowed even if the device is
"up". We don't grab/drop module reference counts when the device is
brought up/down. We simply "down" up net devices at
unregister_netdevice() time.
So if a device is racey, it's going to be "really" racey now.
If people mention which devices give the problems (with current
kernels, we've fixed a lot of bugs as of late) the drivers can
be audited for register/unregister bugs.
next prev parent reply other threads:[~2003-06-30 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 2:35 [BUG]: problem when shutting down ppp connection since 2.5.70 Chris Friesen
2003-06-30 6:07 ` Paul Rolland
2003-06-30 8:05 ` Russell King
2003-06-30 8:03 ` David S. Miller [this message]
2003-06-30 8:23 ` Russell King
2003-06-30 8:42 ` Paul Rolland
2003-06-30 11:18 ` Paul Mackerras
2003-06-30 11:36 ` Paul Mackerras
2003-06-30 14:02 ` Chris Friesen
2003-06-30 15:37 ` Stephen Hemminger
2003-06-30 16:41 ` Chris Friesen
2003-07-01 2:26 ` Chris Friesen
2003-07-03 5:17 ` Chris Friesen
2003-07-06 9:43 ` Paul Rolland
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=20030630.010337.74723316.davem@redhat.com \
--to=davem@redhat.com \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=rol@as2917.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