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: <5d87f4c294be78dc7a4bc39de9883779aba6fa9e.camel@suse.com>
Date: Mon, 22 Dec 2025 11:03:21 +0100
From: Jean DELVARE <jdelvare@...e.com>
To: Crag Wang <crag0715@...il.com>
Cc: dell.client.kernel@...l.com, crag.wang@...l.com, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] firmware: dmi-id: add product_family to modalias as
 pf

Hi Crag,

On Thu, 2025-08-14 at 14:44 +0800, Crag Wang wrote:
> Some devices require product_family information to trigger
> conditional actions when the value matches a predefined criterion
> 
> $ cat /sys/class/dmi/id/product_family
> Dell Pro Max Desktops
> 
> $ udevadm info -q all --path=/sys/class/dmi/id | grep MODALIAS
> E: MODALIAS=dmi:bvnDellInc.:bvr0.59.39:bd12/16/2024:br0.59:efr0.0:svnDellInc.:pfDellProMaxDesktops:pnDellProMaxMicroFCM2250:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0D14:
> 
> $ cat /sys/class/dmi/id/modalias
> dmi:bvnDellInc.:bvr0.59.39:bd12/16/2024:br0.59:efr0.0:svnDellInc.:pfDellProMaxDesktops:pnDellProMaxMicroFCM2250:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0D14:
> 
> Signed-off-by: Crag Wang <crag0715@...il.com>
> ---
>  drivers/firmware/dmi-id.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/firmware/dmi-id.c b/drivers/firmware/dmi-id.c
> index d19c78a78ae3..284652d75cc7 100644
> --- a/drivers/firmware/dmi-id.c
> +++ b/drivers/firmware/dmi-id.c
> @@ -87,6 +87,7 @@ static ssize_t get_modalias(char *buffer, size_t buffer_size)
>  		{ "br",  DMI_BIOS_RELEASE },
>  		{ "efr", DMI_EC_FIRMWARE_RELEASE },
>  		{ "svn", DMI_SYS_VENDOR },
> +		{ "pf",  DMI_PRODUCT_FAMILY },
>  		{ "pn",  DMI_PRODUCT_NAME },
>  		{ "pvr", DMI_PRODUCT_VERSION },
>  		{ "rvn", DMI_BOARD_VENDOR },

For consistency, I'd rather add it between DMI_PRODUCT_VERSION and
DMI_BOARD_VENDOR.

That's simple enough, so why not. Out of curiosity, which udev rule
(and/or driver) needs this?

-- 
Jean Delvare
SUSE L3 Support

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ