linux-kernel - Re: [PATCH 1/4] net: mhi: Rename MHI interface to improve clarity

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: <20250725170855.072f7011@kernel.org>
Date: Fri, 25 Jul 2025 17:08:55 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Vivek.Pernamitta@...cinc.com
Cc: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
 <pabeni@...hat.com>, Manivannan Sadhasivam <mani@...nel.org>,
 <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
 <mhi@...ts.linux.dev>, <linux-arm-msm@...r.kernel.org>, Vivek Pernamitta
 <quic_vpernami@...cinc.com>
Subject: Re: [PATCH 1/4] net: mhi: Rename MHI interface to improve clarity

On Thu, 24 Jul 2025 19:21:17 +0530 Vivek.Pernamitta@...cinc.com wrote:
> From: Vivek Pernamitta <quic_vpernami@...cinc.com>
> 
> Rename the MHI network interface to include the device name, improving
> clarity when multiple MHI controllers are connected.
> 
> Currently, MHI NET device interfaces are created as mhi_swip<n>/
> mhi_hwip<n> for each channel, making it difficult to distinguish between
> channels when multiple EP/MHI controllers are connected.
> 
> Rename the MHI interface to include the device name, for example:
> - Channel IP_SW0 for the 1st MHI controller will be named mhi0_IP_SW0.
> - Channel IP_SW0 for the 2nd MHI controller will be named mhi1_IP_SW0.
> - Channel IP_HW0 for the 1st MHI controller will be named mhi0_IP_HW0.

The userspace can rename the interfaces. It has the association with
the underlying device right there in the udev event.