| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] fix outstanding ref's preventing ether driver unload |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Tue, 23 Dec 2003 15:25:40 -0800 |
| Cc: | dlstevens@xxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20031223151154.01fd002a.shemminger@osdl.org> |
| References: | <OFB4EC53DF.8138874D-ON88256DF9.0082A560@us.ibm.com> <20031223142931.703d5c88.shemminger@osdl.org> <20031223143832.5fe65329.davem@redhat.com> <20031223151154.01fd002a.shemminger@osdl.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 23 Dec 2003 15:11:54 -0800 Stephen Hemminger <shemminger@xxxxxxxx> wrote: > On Tue, 23 Dec 2003 14:38:32 -0800 > "David S. Miller" <davem@xxxxxxxxxx> wrote: > > > Are you going to add such code to RAW, UDP, TCP, etc. etc.? > > They don't have the problem because they don't go through the > netdev_queue_xmit_nit > code path. Audited all calls to dev_add_packet and AF_PACKET is the only > one that I found that could potentially register for ptype_all. > > The same thing could happen through the loopback device, though. > But the loopback device can never be unloaded so it doesn't really > hurt anything. I see, thanks for the clarification.... I have an idea, let me think about this a little bit more. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] fix outstanding ref's preventing ether driver unload, Stephen Hemminger |
|---|---|
| Next by Date: | [PATCH SET] bonding cleanup - take 4, Shmuel Hen |
| Previous by Thread: | Re: [PATCH] fix outstanding ref's preventing ether driver unload, Stephen Hemminger |
| Next by Thread: | Re: [PATCH] fix outstanding ref's preventing ether driver unload, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |