From: Stephen Hemminger <stephen@networkplumber.org>
To: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/1] lib: Align naming rules with the kernel
Date: Fri, 12 Dec 2025 14:03:09 +0900 [thread overview]
Message-ID: <20251212140309.75c84ace@stephen-xps.local> (raw)
In-Reply-To: <20251212042611.786603-1-mail@christoph.anton.mitterer.name>
On Fri, 12 Dec 2025 05:18:12 +0100
Christoph Anton Mitterer <mail@christoph.anton.mitterer.name> wrote:
> I made a small test and compiled iproute2 with its `check_altifname()` simply
> always returning true.
> Turnes out, that the kernel seems to accept any name (i.e. including whitespace
> and `/`) and I didn’t find any check functions for altnames in the kernel
> either (okay I didn’t look that hard ^^).
>
> Not sure, but maybe altnames should really be allowed to contain anything?
> If so, we’d of course need to change this patch.
> OTOH, e.g. systemd already assumes that certain characters aren’t allowed in
> interface names (see `Name=` in systemd.link(5)) and e.g. `nmcli` uses `:` to
> separate fields in its machine readable output.
>
> But then again, the kernel should perhaps check altnames?
The restrictions in the kernel are because interface names also show up in sysfs
which can't allow invalid filenames. The altnames don't show up in sysfs now.
next prev parent reply other threads:[~2025-12-12 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 4:18 [PATCH 0/1] lib: Align naming rules with the kernel Christoph Anton Mitterer
2025-12-12 4:18 ` [PATCH 1/1] " Christoph Anton Mitterer
2025-12-12 4:55 ` Stephen Hemminger
2025-12-12 5:32 ` Christoph Anton Mitterer
2025-12-12 5:03 ` Stephen Hemminger [this message]
[not found] ` <28a0486bd08d59f8f2e758f73a39bd442547197f.camel@christoph.anton.mitterer.name>
[not found] ` <20251213092004.079f9cbe@stephen-xps.local>
2025-12-13 1:48 ` [PATCH 0/1] " Christoph Anton Mitterer
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=20251212140309.75c84ace@stephen-xps.local \
--to=stephen@networkplumber.org \
--cc=mail@christoph.anton.mitterer.name \
--cc=netdev@vger.kernel.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