So, dmidecode directly mmap's to /dev/mem and does some probing based on
the belief that the system is a x86 architecture even on arm
architectures.
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3, {st_mode=S_IFCHR|0640, st_rdev=makedev(0x1, 0x1), ...}) = 0
mmap(NULL, 65536, PROT_READ, MAP_SHARED, 3, 0xf0000) = 0x7f9f6fd000
etc
So that's kind of intrusive and as root one can read any sort of
physical addresses in /dev/mem that may cause breakage.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1858615
Title:
dmidecode triggers system reboot on Inforce 6640
Status in cloud-init:
Invalid
Status in dmidecode package in Ubuntu:
Triaged
Bug description:
Device: Inforce 6640
https://www.inforcecomputing.com/products/single-board-computers-sbc/qualcomm-snapdragon-820-inforce-6640-sbc
SoC: Snapdragon 820
sysname='Linux',
nodename='ubuntu',
release='4.15.0-1069-snapdragon',
version='#76-Ubuntu SMP Tue Nov 26 16:10:14 UTC 2019',
machine='aarch64'
The issue is caused by following commit.
Inforce 6640 doesn't have functional demidecode.
System will reboot when executing dmidecode.
commit 3416e2ee7f65defdb15aab861a85767d13e8c34c
Author: Robert Schweikert <rjsch...@suse.com>
Date: Sat Oct 29 09:29:53 2016 -0400
dmidecode: Allow dmidecode to be used on aarch64
aarch64 systems have functional dmidecode, so allow that to be used.
- aarch64 has support for dmidecode as well
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1858615/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
