public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] utils: do not be restrictive about alternate network device names
Date: Wed, 7 Jan 2026 09:54:18 -0700	[thread overview]
Message-ID: <fa3ba651-67a8-4cde-b9d2-da2d89111341@gmail.com> (raw)
In-Reply-To: <20251221174945.8346-1-stephen@networkplumber.org>

On 12/21/25 10:49 AM, Stephen Hemminger wrote:
> The kernel does not impose restrictions on alternate interface
> names; therefore ip commands should not either.
> 
> This allows colon, slash, even .. as alternate names.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  lib/utils.c | 21 +++++++++++----------
>  1 file changed, 11 insertions(+), 10 deletions(-)
> 

applied to iproute2-next. I wonder if the checks should be removed from
iproute2 and left to the kernel logic to decide if the name is valid.


      reply	other threads:[~2026-01-07 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-21 17:49 [PATCH iproute2] utils: do not be restrictive about alternate network device names Stephen Hemminger
2026-01-07 16:54 ` David Ahern [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa3ba651-67a8-4cde-b9d2-da2d89111341@gmail.com \
    --to=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox