On Fri, 12 Jan 2018, Joseph Salisbury wrote:
> Hi Vikas,
>
> A kernel bug report was opened against Ubuntu [0]. After a kernel
> bisect, it was found that reverting the following commit resolved this bug:
>
> commit 24247aeeabe99eab13b798ccccc2dec066dd6f07
> Author: Vikas Shivappa <[email protected]>
> Date: Tue Aug 15 18:00:43 2017 -0700
>
> x86/intel_rdt/cqm: Improve limbo list processing
>
>
> The regression was introduced as of v4.14-r1 and still exists with
> current mainline. The trace with v4.15-rc7 is in comment #44[1].
>
> I was hoping to get your feedback, since you are the patch author. Do
> you think gathering any additional data will help diagnose this issue,
> or would it be best to submit a revert request?
That stinks like a use after free. Can you run with KASAN enabled?
Thanks,
tglx
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733662
Title:
System hang with Linux kernel due to mainline commit 24247aeeabe
Status in linux package in Ubuntu:
In Progress
Status in linux-hwe package in Ubuntu:
Confirmed
Status in linux source package in Artful:
In Progress
Status in linux-hwe source package in Artful:
Confirmed
Status in linux source package in Bionic:
In Progress
Status in linux-hwe source package in Bionic:
Confirmed
Bug description:
In doing Ubuntu 17.10 regression testing, we've encountered one
computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
four times when running our cpu_offlining test. This test attempts to
take all the CPU cores offline except one, then brings them back
online again. This test ran successfully on boldore with previous
releases, but with 17.10, the system sometimes (about one in four
runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
when I upgraded the 16.04.3 installation to linux-
image-4.13.0-16-generic, the problem appeared again, so I'm confident
this is a problem with the kernel. I'm attaching two files, dmesg-
output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
that appears when running the cpu_offlining test with 4.10.0-38 and
4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
was running "dmesg -w" in a second SSH login; the files are cut-and-
pasted from that.)
I initiated this bug report from an Ubuntu 16.04.3 installation
running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Nov 21 17:36:06 2017
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
