lscpu: Skip aarch64 decode path for rest of the architectures

Bug #2077464 reported by Kim Naru
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Status tracked in Oracular
Noble
New
Undecided
Unassigned
Oracular
New
Undecided
Unassigned

Bug Description

lscpu behaves differently when run sudo vs non-sudo on AMD architectures.

On sudo runs, it adds a BIOS model name and BIOS CPU family which it
does not add for the latter. However since this parsing from the DMI is
primarily catered to aarch64, for AMD platform the BIOS model name is
printed out as follows "AMD XXX Processor *Unknown* CPU @ X.XGHz" due
to the part number is not populated on the platform.

The issue boils down to an unconditional call to arm_decode() which
attempts to read the DMI path and populate the processor information
such as processor version and part number which is set to Unknown on AMD
CPUs.

81d6de9 (lscpu: remove the old code) changed the DMI path from
/sys/firmware/dmi/entries/4-0/raw (non-existent) to
/sys/firmware/dmi/tables/dmi (existent) which has brought this latent
issue to light as DMI was starting to be parsed incorrectly.

Therefore, do not perform aarch64 parsing for other architectures.

https://github.com/util-linux/util-linux/commit/50a3efab6d126b28fcdcc28f1a0cd5cd596ae357

Shengjing Zhu (zhsj)
Changed in linux (Ubuntu):
status: New → Invalid
no longer affects: linux (Ubuntu Noble)
no longer affects: linux (Ubuntu Oracular)
Revision history for this message
Philip Cox (philcox) wrote :

This is a userspace utility in the util-linux package, and not a kernel issue. Removed the kernel from the Affected projects.

no longer affects: linux (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.