yahoo-eng-team team mailing list archive

[dann frazier <dann.frazier@xxxxxxxxxxxxx>]

** Also affects: dmidecode (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: dmidecode (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: dmidecode (Ubuntu Xenial)
     Assignee: (unassigned) => dann frazier (dannf)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
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:
  Fix Released
Status in dmidecode source package in Xenial:
  In Progress
Status in dmidecode source package in Bionic:
  In Progress
Status in dmidecode source package in Eoan:
  In Progress
Status in dmidecode source package in Focal:
  Fix Released
Status in dmidecode package in Debian:
  Unknown

Bug description:
  [Impact]
  Running 'sudo dmidecode' on non-UEFI ARM systems can cause them to crash/reboot. cloud-init apparently runs dmidecode as root, so it breaks any cloud-init based installation.

  [Test Case]
  sudo dmidecode

  [Fix]
  Upstream has the following fix:

  commit e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
  Author: Jean Delvare <jdelvare@xxxxxxx>
  Date: Mon Aug 26 14:20:15 2019 +0200

      dmidecode: Only scan /dev/mem for entry point on x86

  [Regression Risk]
  In Ubuntu, dmidecode only builds on amd64, arm64, armhf & i386.
  The fix is to disable code on !x86, so the regression risk is restricted to ARM platforms, where we know /dev/mem trolling is bad news.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1858615/+subscriptions