mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jengelh@computergmbh.de
Cc: shemminger@linux-foundation.org, helge.hafting@aitel.hist.no,
	olecom@flower.upol.cz, jbeulich@novell.com,
	bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: why network devices don't do reference counting?
Date: Thu, 27 Sep 2007 12:15:22 -0700 (PDT)	[thread overview]
Message-ID: <20070927.121522.52884745.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0709271654270.30621@fbirervta.pbzchgretzou.qr>

From: Jan Engelhardt <jengelh@computergmbh.de>
Date: Thu, 27 Sep 2007 16:55:36 +0200 (CEST)

> 
> On Sep 27 2007 07:51, Stephen Hemminger wrote:
> >
> >You need every socket to close and all routes to go away including the 
> >routes through loopback device, and still there probably are control 
> >sockets buried inside ipv6 that hold ref count.
> >
> >IMHO the kernel should just admit that IPV6 can't be removed.
> 
> I cannot accept that. If ipv6.ko has a way to tack ipv6 structs onto all 
> sockets, interfaces and addresses, it should also be able to untack it 
> again.

Then you do the work and see how incredibly difficult the
implementation is, others have tried.  It's not trivial
and at best it's a very time consuming piece of work to
embark on.

Until then it's un-removable, plain as that :-)

I don't know why we're wasting our fingers discussing this
at all to be honest with you.

  reply	other threads:[~2007-09-27 19:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26  7:53 [PATCH] Module use count must be updated as bridges are created/destroyed Jan Beulich
2007-09-26 15:37 ` Stephen Hemminger
2007-09-26 21:06   ` why network devices don't do reference counting? (Re: [PATCH] Module use count must be updated as bridges are created/destroyed) Oleg Verych
2007-09-26 21:06     ` Stephen Hemminger
2007-09-26 22:18       ` Jan Engelhardt
2007-09-26 22:33         ` Stephen Hemminger
2007-09-26 22:57           ` why network devices don't do reference counting? David Miller
2007-09-27 11:54           ` why network devices don't do reference counting? (Re: [PATCH] Module use count must be updated as bridges are created/destroyed) Helge Hafting
2007-09-27 14:51             ` Stephen Hemminger
2007-09-27 14:55               ` Jan Engelhardt
2007-09-27 19:15                 ` David Miller [this message]
2007-09-27 19:01             ` why network devices don't do reference counting? David Miller
     [not found]   ` <46FAA013.76E4.0078.0@novell.com>
     [not found]     ` <20070926101252.3ccbb987@freepuppy.rosehill>
2007-09-27  7:40       ` [PATCH] Module use count must be updated as bridges are created/destroyed Jan Beulich
2007-09-27 14:48         ` Stephen Hemminger
2007-09-27 15:05           ` Jan Beulich
2007-09-28  5:37             ` Herbert Xu
2007-09-28 18:11               ` Stephen Hemminger
2007-09-29  0:55                 ` Herbert Xu

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=20070927.121522.52884745.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bridge@lists.linux-foundation.org \
    --cc=helge.hafting@aitel.hist.no \
    --cc=jbeulich@novell.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olecom@flower.upol.cz \
    --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

Powered by JetHome