netdev - Re: [RFC] SIOCGIFCOUNT implementation

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: <20070423.142630.21932914.davem@davemloft.net>
Date:	Mon, 23 Apr 2007 14:26:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	shemminger@...ux-foundation.org
Cc:	ak@...e.de, netdev@...r.kernel.org
Subject: Re: [RFC] SIOCGIFCOUNT implementation

From: Stephen Hemminger <shemminger@...ux-foundation.org>
Date: Mon, 23 Apr 2007 14:12:26 -0700

> Trivial implementation of SIOCGIFCOUNT.
> If you search the archives, this was suggested and rejected
> 6 years ago. But there maybe legacy Unix applications that
> could actually use it.
> 
> Signed-off-by: Stephen Hemminger <shemminger@...l.org>

It makes no sense given that you can get this information
with SIOCGIFCONF by supplying a NULL ifc.ifc_buf buffer.
The equivalent of SIOCGIFCOUNT can be obtained by dividing ifc.ifc_len
by the size of one interface entry.

Please also tell me what legacy application could actually
use this thing when BSD itself doesn't even implement it?

A google code search for SIOCGIFCOUNT is fun too.

In fact SIOCGIFCOUNT aparently got removed in 2.2.x, so
let's keep it that way.

There is no reason to add support for this, truly.

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html