group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1699933@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4~0.16.10

---------------
freeipmi (1.4.11-1.1ubuntu4~0.16.10) yakkety; urgency=medium

  * Backport to yakkety
    Use kernel DMI table interface, when available, instead of trolling
    /dev/mem to avoid a crash on ARM. LP: #1699933.

 -- Ike Panhc <ike.pan@xxxxxxxxxxxxx>  Fri, 30 Jun 2017 11:01:05 +0800

** Changed in: freeipmi (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1699933

Title:
  ipmi-locate crash on arm64

Status in freeipmi package in Ubuntu:
  Fix Released
Status in freeipmi source package in Xenial:
  Fix Committed
Status in freeipmi source package in Yakkety:
  Fix Released
Status in freeipmi source package in Zesty:
  Fix Committed
Status in freeipmi source package in Artful:
  Fix Released
Status in freeipmi package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
  not stable to read, it will cause ipmi-locate crash.

  [Test Case]

   * `sudo ipmi-locate` shall not crash

  [Regression Potential]

   * Reading from DMI tables is sysfs is more stable then reading from
  /dev/mem and if DMI tables is not available ipmi-locate will use the
  old way to search in /dev/mem. I believe its low regression risk

  ----
  Similiar to bug 1499838 but not 100% same.

  ipmi-locate looks into /dev/mem for DMI tables and crash when DMI
  tables are not in accessible memory region. Kernel > v4.2 provides
  /sys/firmware/DMI/tables/DMI which is a much safer place to read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1699933/+subscriptions