[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-07-26 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.6 --- util-linux (2.27.1-6ubuntu3.6) xenial; urgency=medium * d/patches/lscpu-make-min-max-freq-arrays-usage-more-robust.patch, d/patches/Avoid-crash-in-min-max-caculation-when-cpu-0-being-o.patch: Cherry pick up

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-27 Thread Francis Ginther
** Tags added: id-5a2eb607f4872474ec5e0a80 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771345 Title: lscpu possible crash in min/max frequency To manage notifications about this bug go to: https

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.32-0.1ubuntu1 --- util-linux (2.32-0.1ubuntu1) cosmic; urgency=low * Merge from Debian unstable. Remaining changes: - Build hwclock with audit support. - Drop debian/hwclock.rules and hwclock.default, recent kernels sync the

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.30.1-0ubuntu4.2 --- util-linux (2.30.1-0ubuntu4.2) artful; urgency=medium * d/patches/Avoid-crash-in-min-max-caculation-when-cpu-0-being-o.patch: Cherry pick upstream patch to avoid SEGV in min/max frequency. LP: #1771345 --

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.31.1-0.4ubuntu3.1 --- util-linux (2.31.1-0.4ubuntu3.1) bionic; urgency=medium * d/patches/Avoid-crash-in-min-max-caculation-when-cpu-0-being-o.patch: Cherry pick upstream patch to avoid SEGV in min/max frequency. LP: #1771345

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-23 Thread Julian Andres Klode
germand/armhf also fails when triggered by gearmand/1.0.6-5.1build2, so it's broken in release. In summary, I don't think any of the autopkgtest regressions are related to these SRUs. It was not expected anyway, given that they only change lscpu code. -- You received this bug notification becaus

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-23 Thread Julian Andres Klode
xenial: nplan/{amd64,i386}: timed out waiting for NetworkManager to settle down, common error nplan/armhf: times out during reboot, also seen for nplan/0.32~16.04.5 postgresql-9.5/armf: fails with stderr "Not all processes could be identified" since 2016-10-17 gearmand/armhf: Unknown failure,

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-23 Thread Julian Andres Klode
artful: nplan/amd64: time outs, reproduce with other triggers too (like systemd/234-2ubuntu12.4) open-iscsi/amd64: times out waiting for network to be configured (same for cloud-utils/0.30-0ubuntu2.1 and others) network-manager: time outs in failure, also happen with systemd trigger, hence not

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-23 Thread Julian Andres Klode
bionic: tracker/i386: retriggered, passed tracker/armhf: retriggered, passed systemd/amd64: timeout in boot-smoke test -> does not seem to be a regression, for example, the most recent boot-smoke also fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which i

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-21 Thread Ɓukasz Zemczak
There are some autopkgtest regressions associated with the bionic, artful and xenial uploads. Could you check if those are real related regressions or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-17 Thread Julian Andres Klode
xenial: 3.4 prints (null), 3.5 crashed, and 3.6 fixed it -> verified artful: 4.1 in release crashes; 4.2 fixes it -> verified bionic: 3 in release crashes, 3.1 fixes it -> verified Sample log from bionic belog: jak@jak-t480s:~/Downloads$ echo lscpu -s /home/jak/Downloads/segvtest | lxc exec b -

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-16 Thread Robie Basak
Hello Julian, or anyone else affected, Accepted util-linux into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util- linux/2.27.1-6ubuntu3.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-16 Thread Julian Andres Klode
Test case ** Attachment added: "segvtest.tar.gz" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1771345/+attachment/5140350/+files/segvtest.tar.gz ** Description changed: [Impact] lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU frequency arrays an

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-16 Thread Julian Andres Klode
** Description changed: - The following fixes are in 2.32 and also need to be backported to - bionic, artful, and xenial: + [Impact] + lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU frequency arrays and can call atof() on them, leading to crashes. It seems that's wh

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-15 Thread Julian Andres Klode
** Changed in: util-linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: util-linux (Ubuntu Artful) Status: New => Triaged ** Changed in: util-linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: util-linux (Ubuntu Bionic) Status: Incomplete => Triage

[Bug 1771345] Re: lscpu possible crash in min/max frequency

2018-05-15 Thread Julian Andres Klode
Merged 2.32, should be building and hitting proposed soon. ** Changed in: util-linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771345 Title: lscpu