netdev - Re: [PATCH net-next] net: uevent: also pass network device driver

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: <20241115140621.45c39269@kernel.org>
Date: Fri, 15 Nov 2024 14:06:21 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Til Kaiser <mail@...54.de>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: uevent: also pass network device driver

On Fri, 15 Nov 2024 19:33:46 +0100 Til Kaiser wrote:
> Currently, for uevent, the interface name and
> index are passed via shell variables.
> 
> This commit also passes the network device
> driver as a shell variable to uevent.

Can you add more information to the commit message for the 'why'?

I'm guessing this can only be used for local one off hacks, or 
can a generic (eg distro level) naming policy benefit from the driver
name?