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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070927.120114.95884344.davem@davemloft.net>
Date:	Thu, 27 Sep 2007 12:01:14 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	helge.hafting@...el.hist.no
Cc:	shemminger@...ux-foundation.org, jengelh@...putergmbh.de,
	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: Helge Hafting <helge.hafting@...el.hist.no>
Date: Thu, 27 Sep 2007 13:54:23 +0200

> Wouldn't it be enough to down all the interfaces and close all the sockets?
> No need to bring down every app.

And there are routes, and neighbour cache entries, and all sorts
of external references to the stack.  For example, if a packet
gets stuck in a device because the link just went down, that
can hold references to the ipv6 module from several angles.

But you have to add code to actually keep track of all of these
references and there is no such code in the ipv6 module at all
and it's a nontrivial time consuming job to implement it.
-
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/