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:   Sat, 10 Aug 2019 06:46:57 -0700
From:   Roopa Prabhu <>
To:     Michal Kubecek <>
Cc:     Jiri Pirko <>, netdev <>,
        David Miller <>,
        Jakub Kicinski <>,
        Stephen Hemminger <>,
        David Ahern <>,,
        Andrew Lunn <>,,
        Saeed Mahameed <>,
        mlxsw <>
Subject: Re: [patch net-next rfc 3/7] net: rtnetlink: add commands to add and
 delete alternative ifnames

On Fri, Aug 9, 2019 at 8:46 AM Michal Kubecek <> wrote:
> On Fri, Aug 09, 2019 at 08:40:25AM -0700, Roopa Prabhu wrote:
> > to that point, I am also not sure why we have a new API For multiple
> > names. I mean why support more than two names  (existing old name and
> > a new name to remove the length limitation) ?
> One use case is to allow "predictable names" from udev/systemd to work
> the way do for e.g. block devices, see

thanks for the link. don't know the details about alternate block
device names. Does user-space generate multiple and assign them to a
kernel object as proposed in this series ?. is there a limit to number
of names ?. my understanding of 'predictable names' was still a single
name but predictable structure to the name.

No strong objections around multiple alternate names as long as the
need for this does not make the base long name setting complex :).

Powered by blists - more mailing lists