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:	Tue, 1 Jul 2014 02:33:19 +0200
From:	Kay Sievers <kay@...y.org>
To:	Thadeu Lima de Souza Cascardo <cascardo@...ux.vnet.ibm.com>
Cc:	systemd-devel@...ts.freedesktop.org, netdev@...r.kernel.org
Subject: Re: [systemd-devel] [PATCH] Use dev_port for the ID of a network device.

On Mon, Jun 30, 2014 at 10:36 PM, Thadeu Lima de Souza Cascardo
<cascardo@...ux.vnet.ibm.com> wrote:
> For network devices on the same PCI function, dev_id should not be used,
> since its purpose is for IPv6 support on interfaces with the same MAC
> address.
>
> The new dev_port sysfs attribute should be used when it is found. When
> it is not, using dev_id might work.

I don't see a problem switching this over, but why would we keep using
dev_id if it is not the right thing to use?

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

Powered by blists - more mailing lists