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: <20241116163206.7585-1-mail@tk154.de>
Date: Sat, 16 Nov 2024 17:30:29 +0100
From: Til Kaiser <mail@...54.de>
To: kuba@...nel.org
Cc: netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: uevent: also pass network device driver

Hi, thanks for the response.

I have added a short explanation to the commit message.

I aim to retrieve the network interface's driver when it
gets created on the Linux OpenWrt OS. OpenWrt doesn't use
udev but uses its own hotplug implementation where the driver
name isn't available per a shell variable.

As I mentioned in my commit message, I could add the driver
query to the hotplug implementation. But I think it might also
be beneficial for other Linux OS that the driver name comes
directly from the Linux Kernel.

Furthermore, I think it's more comfortable for a user that he
can directly check the driver name through the sysfs uevent file.

Kind regards
Til

Changes in v2:
 - Updated the commit message to clarify the purpose of the patch.