ubuntu@rare-fowl:~$ sudo dpkg -i --force-depends --auto-deconfigure util-linux_2.28.2-1ubuntu1.1_arm64.deb ... ubuntu@rare-fowl:~$ sudo lscpu Segmentation fault (core dumped) ubuntu@rare-fowl:~$ sudo dpkg -i --force-depends --auto-deconfigure util-linux_2.28.2-1ubuntu1.2_arm64.deb ... ubuntu@rare-fowl:~$ sudo lscpu Architecture: aarch64 Byte Order: Little Endian CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 16 NUMA node(s): 4 NUMA node0 CPU(s): 0-15 NUMA node1 CPU(s): 16-31 NUMA node2 CPU(s): 32-47 NUMA node3 CPU(s): 48-63
-- 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 Committed Status in util-linux source package in Yakkety: Fix Committed Status in util-linux source package in Zesty: Fix Committed 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
