linux-kernel - Re: [PATCH v1] mod_devicetable: Bump auxiliary_device

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2025110105-upright-dinginess-3b2c@gregkh>
Date: Sat, 1 Nov 2025 07:18:22 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Raag Jadav <raag.jadav@...el.com>
Cc: kees@...nel.org, broonie@...nel.org, arnd@...db.de,
	andriy.shevchenko@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] mod_devicetable: Bump auxiliary_device_id name size

On Sat, Nov 01, 2025 at 12:32:34AM +0530, Raag Jadav wrote:
> Since auxiliary device id string is formed using the combination of parent
> and child device names, it may require more than 32 bytes if both the names
> are long enough. Bump the size to 40 bytes to satisfy such cases.

What in-kernel users need such a larger name?  If we allow larger names,
people will try to do crazy things and use memory addresses in them (has
happened already...)

> Suggested-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> Signed-off-by: Raag Jadav <raag.jadav@...el.com>
> ---
> Triggered by [1].
> 
> [1] https://lore.kernel.org/r/aQSwWLVKH_3TthTW@smile.fi.intel.com

How long would this driver submission's name be?  I couldn't figure it
out, and really, any device with a huge name is going to be a pain...

thanks,

greg k-h