netdev - Re: [PATCH 00/10 net-next] Introduce per interface ipv4 statistics

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 16 Dec 2011 13:31:53 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	igorm@....rs, netdev@...r.kernel.org
Subject: Re: [PATCH 00/10 net-next] Introduce per interface ipv4 statistics

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Fri, 16 Dec 2011 17:33:04 +0100

> Le vendredi 16 décembre 2011 à 16:58 +0100, Igor Maravić a écrit :
>> Also I did it because ipv6 has per interface stats.
> 
> I was considering _removing_ them, or make it optional.

It is not the only huge problem with this feature.

The other one is, as I said, it requires having some inetdev available in
every single corner of every packet processing path, just so we can hit
some statistic.

Which means we have all of this special case code to make sure we have at
least a reference to the loopback device when a physical device is brought
down or removed.

It's painful, ugly, and not something I want propagating into ipv4 as well.

There is no way I'm letting this feature in, I've already wasted enough time
when trying to make ipv6 changes because of this facility.