netdev - [PATCH net-next 0/3] net, net/mlx4: Add sysfs file for port number

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

Date:	Tue, 25 Feb 2014 18:17:49 +0200
From:	Amir Vadai <amirv@...lanox.com>
To:	"David S. Miller" <davem@...emloft.net>
Cc:	Or Gerlitz <ogerlitz@...lanox.com>,
	Yevgeny Petrilin <yevgenyp@...lanox.com>,
	Amir Vadai <amirv@...lanox.com>, netdev@...r.kernel.org,
	Jordan_Hargrave@...l.com, Narendra_K@...l.com
Subject: [PATCH net-next 0/3] net, net/mlx4: Add sysfs file for port number

Hi,

Modern distro's are using biosdevname to rename interface to a name based on
slot/port number.
biosdevname can't get the port number of devices that have multiple ports that
share the same PCI function.
This patch adds a sysfs file under: /sys/devices/.../net/<interface>/dev_port,
that contains the port number (0 based) - to be used by biosdevname.
Also, dev_id was wrongly used in mlx4_en driver - added a patch that fix it.

This patch was tested and applied over commit 51adfcc "net: bcmgenet: remove
unused bh_lock member"

Amir

CC: Jordan_Hargrave@...l.com 
CC: Narendra_K@...l.com

Amir Vadai (3):
  net: Add sysfs file for port number
  net/mlx4_en: Expose port number through sysfs
  net/mlx4_en: Fix bad use of dev_id

 drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 2 +-
 include/linux/netdevice.h                      | 4 ++++
 net/core/net-sysfs.c                           | 2 ++
 3 files changed, 7 insertions(+), 1 deletion(-)

-- 
1.8.3.4

--
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