netdev - RE: [PATCH net-next] net: Add phys_port identifier to struct net

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]

Date:	Wed, 19 Jun 2013 16:37:56 -0500
From:	<Praveen_Paladugu@...l.com>
To:	<bhutchings@...arflare.com>, <Narendra_K@...l.com>
CC:	<john.fastabend@...il.com>, <netdev@...r.kernel.org>,
	<john.r.fastabend@...el.com>
Subject: RE: [PATCH net-next] net: Add phys_port identifier to struct
 net_device and export it to sysfs

Having an unique identifier per port, the userspace tools might be able to check if the VFs/partitions are of the same physical port. Just being paranoid, wouldn't it be better to bond VFs/Partitions across NICs instead of across ports of the same NIC?

To be able to check if the VFs/partitions are of the same port & NIC, the unique identifier should probably have two identifiers  in it like ABC_XYZ. The ABC uniquely identifying the NIC and XYZ uniquely identifying the port.   

Any thoughts?

Thank you 
Praveen K Paladugu