linux-kernel - Re: why network devices don't do reference counting?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070927.121522.52884745.davem@davemloft.net>
Date:	Thu, 27 Sep 2007 12:15:22 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jengelh@...putergmbh.de
Cc:	shemminger@...ux-foundation.org, helge.hafting@...el.hist.no,
	olecom@...wer.upol.cz, jbeulich@...ell.com,
	bridge@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: why network devices don't do reference counting?

From: Jan Engelhardt <jengelh@...putergmbh.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/