** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1755627
Title:
ibrs/ibpb fixes result in excessive kernel
This bug was fixed in the package linux - 4.13.0-43.48
---
linux (4.13.0-43.48) artful; urgency=medium
* CVE-2018-3639 (powerpc)
- SAUCE: rfi-flush: update H_CPU_* macro names to upstream
- SAUCE: rfi-flush: update plpar_get_cpu_characteristics() signature to
upstream
This bug was fixed in the package linux - 4.13.0-43.48
---
linux (4.13.0-43.48) artful; urgency=medium
* CVE-2018-3639 (powerpc)
- SAUCE: rfi-flush: update H_CPU_* macro names to upstream
- SAUCE: rfi-flush: update plpar_get_cpu_characteristics() signature to
upstream
This bug was fixed in the package linux - 3.13.0-149.199
---
linux (3.13.0-149.199) trusty; urgency=medium
* CVE-2018-3639 (powerpc)
- SAUCE: rfi-flush: update H_CPU_* macro names to upstream
- SAUCE: rfi-flush: update plpar_get_cpu_characteristics() signature to
This bug was fixed in the package linux - 3.13.0-149.199
---
linux (3.13.0-149.199) trusty; urgency=medium
* CVE-2018-3639 (powerpc)
- SAUCE: rfi-flush: update H_CPU_* macro names to upstream
- SAUCE: rfi-flush: update plpar_get_cpu_characteristics() signature to
This bug was fixed in the package linux - 4.4.0-127.153
---
linux (4.4.0-127.153) xenial; urgency=medium
* CVE-2018-3639 (powerpc)
- powerpc/pseries: Support firmware disable of RFI flush
- powerpc/powernv: Support firmware disable of RFI flush
- powerpc/rfi-flush: Move
Indeed, the -proposed kernel versions which included this fix were all
bumped out due to an unrelated security fix release. The next kernel
versions (now available in -proposed) include the fix again:
trusty 3.13.0-148.197
xenial 4.4.0-125.150
artful 4.13.0-42.47
--
You received this bug
It looks like it got deferred to 4.4.0-125 according to the changelog
[1].
[1] https://launchpad.net/ubuntu/+source/linux/4.4.0-125.150
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I am still experiencing this issue after upgrading to xenial 16.04.4 LTS
4.4.0-124-generic.
--
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/1755627
Title:
ibrs/ibpb fixes result in
Hello.
I just wanto to confirm: everything seems to be okay after updating
Linux kernel to v4.4.0-123-generic. However, I would like to ask a
question about 'intel-microcode' and 'amd64-microcode' packages. During
system updating process via apt(8), there was an information that "The
following
Verified fixed in all affected -proposed kernels:
trusty 3.13.0-146.195
xenial 4.4.0-123.147
artful 4.13.0-40.45
** Tags removed: verification-needed-artful verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done-artful verification-done-trusty
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
Hello.
Yes, Mr. Kamal Mostafa is right. Linux kernel v4.4.0-123.147 will
contain a fix for all of these issues with, for example,
'/var/log/syslog' flooding with 'ibrs_dump', 'use_ibrs/ibpb' and
'sysctl_ibrs{,ibpb}_enabled' entries. Now, a "proposed" kernel is
v4.4.0-122.146 with a fix for
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag
Is the fixed kernel available right now? Or when could it be available?
This "ubrs" messages are flooding our syslog log files on many machines.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Just FYI folks: This fix does not yet appear in the kernels which just
landed in -proposed (which are respins for an unrelated issue). The fix
is still queued up for the next cycle (currently 4.4.0-123.147).
--
You received this bug notification because you are a member of Kernel
Packages,
Hello.
Today, I noticed the same entries in a log files such as
'/var/log/syslog' and via dmesg(1) on 16.04 LTS Release (i386/x86_32
arch) with v4.4.0-120-generic (4.4.117) Linux kernel. The one thing,
that is different is 'use_ibrs' value. In my case it's:
[~]$ sudo dmesg
[ 464.877859]
Hello,
The same here:
Apr 18 06:29:16 ovh-staging-rancher-docker-10 kernel: [37874.285196]
sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 18 06:29:16 host kernel: [37874.285197] use_ibrs = 4, use_ibpb = 4
Apr 18 06:29:16 host kernel: [37874.285202] read cpu 0 ibrs val 0
Apr 18 06:29:16
@lscotte - Thanks for reporting the issue. Launchpad will post a note
to this bug as soon as the kernel versions containing the fix reach the
-proposed archive.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thank you @kamalmostafa - we'll keep an eye out for the updated packages
in the repositories and follow up if anything is not as expected. Thanks
again for fixing this!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@bmoyles- FYI, we're just removing the kernel.ibrs_dump interface
altogether -- its only purpose is to provide that debug info, and
nothing like it made it to mainline.
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification
** Changed in: linux (Ubuntu Trusty)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa
(kamalmostafa)
** Changed in: linux (Ubuntu Xenial)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa
(kamalmostafa)
** Changed in: linux (Ubuntu
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/kernel/sysctl.c#n2433
and
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/kernel/sysctl.c#n2446
are the source(s) of the noise
Looking at nearby functions like proc_dointvec_ibrs_ctrl
Thank you Leann!
--
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/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
Status in linux package in Ubuntu:
Confirmed
Status
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Triaged
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) =>
Also, to call it out again, this appears to affect Trusty's LTS kernel,
too (it's not clear how one marks a bug as such from the Launchpad UI)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For the sake of completeness on this one, I installed the following
mainline packages on an AWS m5.large instance running 16.04.3 w/
4.4.0-112-generic
- linux-headers-4.16.0-041600rc4_4.16.0-041600rc4.201803041930_all.deb
-
It's worth noting, too, that this does not happen on Bionic @ 4.15
(using Ubuntu 4.15.0-1001.1-aws 4.15.3) but it does happen on Trusty
(using Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Returning to confirmed status - easily reproducible with LTS kernels.
--
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/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
We use LTS kernels, so no - unfortunately we cannot.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
We do not use apport and this is easily reproducible. If there is any
pointed information I can provide beyond what I've already submitted,
please let me know.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
34 matches
Mail list logo
