This bug was fixed in the package util-linux - 2.28.2-1ubuntu1.2
---------------
util-linux (2.28.2-1ubuntu1.2) yakkety; urgency=medium
* Cherrypick upstream fix to prevent lscpu crash on arm64 by
accessing DMI in sysfs instead of /dev/mem. LP: #1674258
-- Ike Panhc <ike....@canonical.com> Thu, 18 May 2017 10:49:34 +0800
** Changed in: util-linux (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
** Changed in: util-linux (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674258
Title:
lscpu crashs when /dev/mem is not stable to read
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Xenial:
Fix Released
Status in util-linux source package in Yakkety:
Fix Released
Status in util-linux source package in Zesty:
Fix Released
Bug description:
[Impact]
* Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
not stable to read, it will cause lscpu crash.
[Test Case]
* `sudo lscpu` shall not cause Segmentation fault (core dumped)
[Regression Potential]
* Reading from DMI tables is sysfs is more stable then reading from
/dev/mem and if DMI tables is not available lscpu will use the old way
to search in /dev/mem. I believe its low regression risk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1674258/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
