netdev - Re: [RFC] Enhance dev_ioctl to return <hwaddr>:<if_name::if

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: <20100716.131835.124042396.davem@davemloft.net>
Date:	Fri, 16 Jul 2010 13:18:35 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	chetanloke@...il.com
Cc:	shemminger@...tta.com, Chetan.Loke@...scout.com,
	bhutchings@...arflare.com, netdev@...r.kernel.org
Subject: Re: [RFC] Enhance dev_ioctl to return <hwaddr>:<if_name::if_index>
 mapping

From: Chetan Loke <chetanloke@...il.com>
Date: Fri, 16 Jul 2010 16:15:44 -0400

> Ok, what if, i) ifindex == 0 in the call to SIOCGIFINDEX or ii) if the
> ifindex is not found ? May be then in the else clause we could search
> using the hw-addr before bailing out ;)? This way we can avoid adding
> a new API. Still not a good idea?

I'm really not going to consider this seriously, sorry.  I've
made my position pretty clear, and gave sufficient reasons for
it.

Myself and others have also shown you several ways to fetch the
information you need, and of them netlink is probably the most
efficient, but the others work just as well.

The new interface proposals are just not a good idea.
--
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