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] [day] [month] [year] [list]
Message-ID: <aV504ARc3u-4lRL5@gaggiata.pivistrello.it>
Date: Wed, 7 Jan 2026 15:59:44 +0100
From: Francesco Dolcini <francesco@...cini.it>
To: Chen-Yu Tsai <wenst@...omium.org>
Cc: Brian Norris <briannorris@...omium.org>,
	Francesco Dolcini <francesco@...cini.it>,
	Johannes Berg <johannes.berg@...el.com>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] wifi: mwifiex: Allocate dev name earlier for interface
 workqueue name

On Wed, Jan 07, 2026 at 05:27:40PM +0800, Chen-Yu Tsai wrote:
> The interface specific workqueues are allocated with the interface name
> as part of the workqueue name. However when they are allocated, the
> interface name has not been allocated, thus the "name" is actually the
> pattern for the name "mlan%d". This ends up pretty ugly and could
> conflict if multiple interfaces were added.
> 
> Allocate the device name earlier and use that to allocate the
> workqueues. Also tweak the workqueue name patterns to add a separator
> between the prefix and the interface name parts for readability.

Is there any impact on this approach when/if the interface is renamed from
userspace?

Francesco


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ