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: <CAM_iQpVmy4bAKB9jwd0+uetw6GZuxg4MOmOb4Zya31VUwRYDQQ@mail.gmail.com>
Date:	Thu, 12 May 2016 13:19:34 -0700
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	Chris Friesen <cbf123@...l.usask.ca>
Cc:	Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: where is the ethernet device number determined?

On Thu, May 12, 2016 at 1:05 PM, Chris Friesen <cbf123@...l.usask.ca> wrote:
>
> Hi,
>
> I hope this is a simple question...with legacy naming ethernet devices are
> named ethX.  Where is that X determined?  I've been looking in
> alloc_netdev_mqs() and friends, but haven't found it yet.

__dev_alloc_name()

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ