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
| ||
|
Message-ID: <597da6f1-c0fc-ae23-94d1-d0fb3abb3176@redhat.com> Date: Mon, 13 Mar 2017 19:45:50 -0400 From: Jarod Wilson <jarod@...hat.com> To: netdev <netdev@...r.kernel.org> Cc: Jay Vosburgh <j.vosburgh@...il.com> Subject: bond procfs hw addr prints I've got a bug report for someone using a Intel OPA devices in a bond, and it appears these devices have a hardware address length of 20, opposed to the typical 6 on ethernet. When they dump /proc/net/bonding/bondX, it only prints the first 6 of the address, per %pM and mac_address_string(), while sysfs for the interface does print the right thing, since it uses sysfs_print_mac(), which takes a length argument. So the question is... What's the best route to take here? Expand %pM to support variable length hardware addresses? Use sysfs_* in procfs? Reinvent the wheel? Nothing I've tinkered with just yet feels very clean, on top of not actually working yet. :) -- Jarod Wilson jarod@...hat.com
Powered by blists - more mailing lists