From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7B6C4C433FF for ; Mon, 12 Aug 2019 15:43:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5348A20679 for ; Mon, 12 Aug 2019 15:43:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726543AbfHLPnw (ORCPT ); Mon, 12 Aug 2019 11:43:52 -0400 Received: from mx2.suse.de ([195.135.220.15]:60112 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726515AbfHLPnw (ORCPT ); Mon, 12 Aug 2019 11:43:52 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id DC0E3AE20; Mon, 12 Aug 2019 15:43:50 +0000 (UTC) Received: by unicorn.suse.cz (Postfix, from userid 1000) id 2D859E013A; Mon, 12 Aug 2019 17:43:49 +0200 (CEST) Date: Mon, 12 Aug 2019 17:43:49 +0200 From: Michal Kubecek To: netdev@vger.kernel.org Cc: Roopa Prabhu , Jiri Pirko , David Miller , Jakub Kicinski , Stephen Hemminger , David Ahern , dcbw@redhat.com, Andrew Lunn , parav@mellanox.com, Saeed Mahameed , mlxsw Subject: Re: [patch net-next rfc 3/7] net: rtnetlink: add commands to add and delete alternative ifnames Message-ID: <20190812154349.GE30089@unicorn.suse.cz> References: <20190719110029.29466-4-jiri@resnulli.us> <20190809062558.GA2344@nanopsycho.orion> <20190809154609.GG31971@unicorn.suse.cz> <20190810155042.GA30089@unicorn.suse.cz> <20190811221027.GD30089@unicorn.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Aug 12, 2019 at 08:21:31AM -0700, Roopa Prabhu wrote: > On Sun, Aug 11, 2019 at 3:10 PM Michal Kubecek wrote: > > > > Not all of them are hardware based, there are also links based on > > filesystem label or UUID. But my point is rather that udev creates > > multiple links so that any of them can be used in any place where > > a block device is to be identified. > > > > As network devices can have only one name, udev drops kernel provided > > name completely and replaces it with name following one naming scheme. > > Thus we have to know which naming scheme is going to be used and make > > sure it does not change. With multiple alternative names, we could also > > have all udev provided names at once (and also the original one from > > kernel). > > ok, understand the use-case. > But, Its hard for me to understand how udev is going to manage this > list of names without structure to them. > Plus how is udev going to distinguish its own names from user given name ?. > > I thought this list was giving an opportunity to use the long name > everywhere else. > But if this is going to be managed by udev with a bunch of structured > names, I don't understand how the rest of the system is going to use > these names. > > Maybe we should just call this a udev managed list of names. > > (again, i think the best way to do this for udev is to provide the > symlink like facility via devlink or any other infra). I certainly didn't want to suggest for alternative names to be managed by udev. What I meant was that supporting multiple alternative names would allow udev to create its names based on e.g. device bus address, BIOS/UEFI slot number, MAC address etc. But it would still be up to admins if they want to create their own names. Michal