I'm not able to reproduce this on a physical host. Works just fine for
all the 32-bit kernels that I tested. When you say 'black screen', do
you not get anything at all? Not even some BIOS flickering in the
beginning?
What do you get when you run the following:
$ qemu-system-i386 -cdrom xubuntu-18
Boot tested on relevant HW.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1789215
Title:
i40e NIC no
** Changed in: linux (Ubuntu)
Status: Expired => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
** Description changed:
+ == SRU Justification ==
+
Ubunt
*** This bug is a duplicate of bug 1765232 ***
https://bugs.launchpad.net/bugs/1765232
Marking this as a duplicate of #1765232.
** This bug has been marked a duplicate of bug 1765232
Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers
--
You received this bug notification because you
*** This bug is a duplicate of bug 1765232 ***
https://bugs.launchpad.net/bugs/1765232
4.15.0-19 works OK, 4.15.0-18 is broken.
The problems was introduced in -14 with the following 2 commits:
* 9403a13fd07e blk-mq: simplify queue mapping & schedule with each possisble
CPU
* f0aff9ccc834
Public bug reported:
When booting in secure boot mode, the Bionic kernel emits the following message:
[ 52.035055] Lockdown: Loading of unsigned modules is restricted; see man
kernel_lockdown.7
But there is no such man page.
** Affects: linux (Ubuntu)
Importance: Undecided
Statu
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Skipped the following commit (commit to be reverted is not applied):
* Revert "perf tests: Decompress kernel module before objdump"
--
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/1768429
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Skipped the following patch (already applied):
* KVM: s390: wire up bpb feature
--
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/1768474
Title:
Xenial update to 4.4.130 stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable
Skipped the following commits:
* ALSA: hda: Hardening for potential Spectre v1
* ALSA: seq: oss: Hardening for potential Spectre v1
* ALSA: control: Hardening for potential Spectre v1
* ALSA: rme9652: Hardening for potential Spectre v1
* ALSA: hdspm: Hardening for potential Spectre v
Hi Breno,
Sorry for the late reply. Regarding Xenial, we updated the kernel to a
later upstream stable version since you posted the patches.
4.4.0-123.147 from -proposed should be in sync with 4.4.128 now and your
patches don't apply cleanly any longer. When updating to 4.4.117 we
reverted a bunch
** Summary changed:
- artful: rfi-flush: Switch to new linear fallback flush
+ rfi-flush: Switch to new linear fallback flush
--
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/1744173
Title:
** Description changed:
+ [Impact]
Change flush from congruence-first with dependencies to linear with
no dependencies, which increases flush performance by 8x on P8, and
3x on P9 (as measured with null syscall loop, which will have the
flush area in the L2).
The flush also becomes si
Public bug reported:
Ubuntu kernels contain Meltdown and Spectre mitigations that are largely
based on embargoed patches but what eventually landed in upstream is
different in some places. We should cleanup the different kernels to
bring them closer in line with upstream.
** Affects: linux (Ubunt
Public bug reported:
Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")
This causes cloud-init to stall for a potentially long time during boot
(waiting for entropy I presume). Google reported boot delays of 75
minutes.
I've tracked
mvo: fwiw jinja2 imports random and that reads 2500 chars from
/dev/urandom on import
--
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/1780062
Title:
Cloud-init causes potentially huge boo
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Chances are slim that this will fix itself automagically. And as long as we're
not able to reproduce this, it's going to be difficult. I'll try to take
another look in a couple of days once
the current kernel respin frenzy is over.
--
You received this bug notification because you are a member
** Description changed:
- This bug is for tracking the upload package. This
- bug will contain status and testing results related to that upload.
+ This bug is for tracking the 4.15.0-1015.17 upload package. This bug
+ will contain status and testing results related to that upload.
For an ex
Jose, I'm confused. I never provided a kernel with the patches from
comment #8 yet you did some testing and need a follow-on patch? What
kernel did you test?
Also, this ticket is closed as "won't fix" so you should not add new
requests to it. And since the patches are for the ibm-gt kernel (which
Public bug reported:
Booting an i386 Bionic kernel in a VM leads to:
[1.074702] Freeing unused kernel memory: 1092K
[1.084027] Write protecting the kernel text: 8836k
[1.085115] Write protecting the kernel read-only data: 3480k
[1.086361] NX-protecting the kernel data: 7548k
[
** Description changed:
- Booting an i386 Bionic kernel in a VM leads to:
+ == SRU Justification ==
+
+ Booting an i386 Bionic kernel in a VM with a 64-bit CPU leads to:
[1.074702] Freeing unused kernel memory: 1092K
[1.084027] Write protecting the kernel text: 8836k
[1.08511
Public bug reported:
Booting Bionic i386 in a VM and running the following commands
repeatedly:
ovs-vsctl add-br test
ovs-vsctl del-br test
eventually leads to:
[ 44.476751] IP: kmem_cache_alloc_trace+0x91/0x1d0
[ 44.477299] *pdpt = 1ae13001 *pde =
[ 44.477956]
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
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/1814054
Title:
BUG: unable to handle kernel pag
eam) => Juerg Haefliger
(juergh)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger
(juergh)
** Changed in: kernel-
(canonical-hw-cert)
Status: Invalid
** Affects: kernel-sru-workflow/prepare-package
Importance: Medium
Assignee: Juerg Haefliger (juergh)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-meta
Importance: Medium
Assignee: Juerg Haefliger (juergh
*** This bug is a duplicate of bug 1815061 ***
https://bugs.launchpad.net/bugs/1815061
** This bug has been marked a duplicate of bug 1815061
linux-ibm-gt: -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Successfully tested both 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/1813532
Title:
x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a
Status in linux package
Tested successfully.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1812086
Title:
kernel BUG at /bui
Successfully tested Xenial, Bionic and Cosmic kernels.
** Tags removed: verification-needed-bionic verification-needed-cosmic
verification-needed-xenial
** Tags added: verification-done-bionic verification-done-cosmic
verification-done-xenial
--
You received this bug notification because you a
Verified that all commits are applied.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1811646
Title:
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1788817
Title:
BUG: soft lockup - CPU#0 stuck for 23s!
Public bug reported:
Running a set of autotests on Trusty with kernel 3.13.0-160-generic
results in the following reproducible crash:
[10870.247844] kernel BUG at
/build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!
[10870.255080] invalid opcode: [#1] SMP
[10870.259339] Modules linked in:
Turns out that it is the cpu hotplug kernel selftest that crashes the kernel.
Simply run:
$ bash tools/testing/selftests/cpu-hotplug/on-off-test.sh
from the Trusty 3.13 tree and the machine will fall over a couple of minutes
later.
--
You received this bug notification because you are a member
Works fine in a VM.
--
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/1795675
Title:
kernel BUG at /build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!
Status in linux package in Ubuntu:
eam) => Juerg Haefliger
(juergh)
** Changed in: kernel-sru-workflow/prepare-package-lbm
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-lbm
Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger
(juergh)
** Changed in: kernel-
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => Won't Fix
** Changed in: linux (Ubuntu Bionic)
Status: Fix Released => Won't Fix
--
The kernel patches were delivered via a custom kernel.
--
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/1800649
Title:
Add support for NVIDIA GPU passthrough
Status in linux package in Ub
nel Team (canonical-kernel-team) => Juerg Haefliger
(juergh)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefli
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Released => In Progress
--
https://lists.ubuntu.com/archives/kernel-team/2018-October/096352.html
** Project changed: qemu-kvm => linux
** Project changed: linux => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Ran the Trusty -proposed kernel through some basic tests, looks good.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Juerg Haefliger (juergh)
Status: New
** Tags: kernel-stable-tracking-bug
** Tags added: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
** Description changed:
+ SRU Justification
- SRU Justification
+
Skipped the following patches (already applied):
* powerpc/fadump: Return error when fadump registration fails
--
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/1801893
Title:
Xenial update
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Skipped the following patches (already applied):
* Drivers: hv: utils: Invoke the poll function after handshake
* Drivers: hv: util: Pass the channel information during the init call
* Drivers: hv: kvp: fix IP Failover
--
You received this bug notification because you are a member of Kernel
I talked to the security team. There is no reason to check for
CONFIG_RETPOLINE != 'y' in Precise. CONFIG_RETPOLINE should always be
set to 'y', even if the toolchain doesn't support it. There are minimal
mitigations that we get even without toolchain support but for that we
need CONFIG_RETPOLINE e
** Summary changed:
- Add support to NVIDIA GPU passthrough
+ Add support for NVIDIA GPU passthrough
--
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/1800649
Title:
Add support for NVIDIA
** Changed in: linux (Ubuntu Precise)
Status: New => In Progress
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Precise)
Status: New => In Progress
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
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/1800649
Title:
Add support for NVIDIA GPU passthrough
Status in
Public bug reported:
Running the kernel net tls selftests on 5.0 produces:
# tools/testing/selftests/net/tls
[==] Running 28 tests from 2 test cases.
[ RUN ] tls.sendfile
[ OK ] tls.sendfile
[ RUN ] tls.send_then_sendfile
[ OK ] tls.send_then_sendfile
[ RUN ] tl
tls.recv_peek_large_buf_mult_recs is a new test that never passed (for
upstream). It tests a functionality (mult-record PEEk) that hasn't been
(properly) implemented yet.
https://lkml.org/lkml/2018/9/18/847
** Changed in: linux (Ubuntu Disco)
Status: New => Confirmed
--
You received this
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
After doing some bisection I found the following commit to introduce the
problem:
120645513f55a4ac5543120d9e79925d30a0156f is the first bad commit
commit 120645513f55a4ac5543120d9e79925d30a0156f
Author: Jarno Rajahalme
Date: Fri Apr 21 16:48:06 2017 -0700
openvswitch: Add eventmask support
125.361728] CR2: 0074
[ 125.362329] ---[ end trace ce5d2e276f1f9782 ]---
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: Juerg Haefliger (juergh)
Status: Incomplete
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You r
*** This bug is a duplicate of bug 1736390 ***
https://bugs.launchpad.net/bugs/1736390
** This bug has been marked a duplicate of bug 1736390
openvswitch: kernel oops destroying interfaces on i386
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
List of already applied patches:
* xfs: don't fail when converting shortform attr to long form during
ATTR_REPLACE
--
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/1818797
Title:
Xenial
Skipped the following patches (modifications already applied via SAUCE patches):
* proc: Remove empty line in /proc/self/status
--
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/1818797
Tit
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
List of already applied patches:
* KVM: x86: work around leak of uninitialized stack contents (CVE-2019-7222)
* KVM: nVMX: unconditionally cancel preemption timer in free_nested
(CVE-2019-7221)
* igb: Fix an issue that PME is not enabled during runtime suspend
--
You received this bug noti
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
List of already applied patches:
* kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)
--
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/1818815
Title:
Xenial update: 4.
Skipped the following patches (modifications already applied previously):
* KVM: VMX: Fix x2apic check in vmx_msr_bitmap_mode()
--
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/1818815
Tit
https://lore.kernel.org/lkml/20190305104010.6342e9b9@gollum/
** Also affects: linux (Ubuntu Disco)
Importance: High
Status: In Progress
** Also affects: openvswitch (Ubuntu Disco)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a m
** Description changed:
+ == SRU Justification ==
+
+ Commit 120645513f55 ("openvswitch: Add eventmask support to CT action.")
+ introduced a regression on i386. Simply running the following commands
+ in a loop will trigger a crash rather quickly:
+
+ ovs-vsctl add-br test
+ ovs-vsctl del-br te
The commit that added the test has been reverted.
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Committed
--
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/1816716
Titl
Can you please give this test kernel a try:
https://kernel.ubuntu.com/~juergh/lp1804149/
--
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/1804149
Title:
Kernel panic,Oops: 0004 ilc:3 [#1]
Xenial's implementation has been update via updates to newer 4.4
upstream stable versions.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
List of previously applied patches:
* gro: Allow tunnel stacking in the case of FOU/GUE
* tpm: fix: return rc when devm_add_action() fails
* ixgbe: Correct X550EM_x revision check
* ixgbe: fix RSS limit for X550
* ixgbevf: Fix handling of NAPI budget when multiple queues are enabled per
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
List of previously applied patches:
* cdrom: fix improper type cast, which can leat to information leak.
* mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts
* mount: Retest MNT_LOCKED in do_umount
* HID: hiddev: fix potential Spectre v1
--
You received this bug notification beca
Correction, the following patch has not been applied previously:
* HID: hiddev: fix potential Spectre v1
There is an older commit with the same subject but different content,
hence the confusion.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Skipped the following commit:
* Revert "Bluetooth: h5: Fix missing dependency on BT_HCIUART_SERDEV"
The commit that is reverted was never added to Xenial 4.4.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Already applied patches:
* mm: mlock: avoid increase mm->locked_vm on mlock() when already
mlock2(,MLOCK_ONFAULT)
--
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/1811077
Title:
Xenial
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
List of already applied patches:
* posix-timers: Sanitize overrun handling
* KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
* x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
* x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
* x86: Introduce __uaccess_b
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
The update to stable 4.4.169 will fix the majority of the issue.
--
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/1764956
Title:
Guests using IBRS incur a large performance penalty
Status
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
== SRU Justification ==
The update to stable 4.4.169 contains a couple of x86/kvm related
commits that have later fixup commits in upstream.
== Fix ==
Cherry-pick or backport the relevant commits.
== Regression Potential ==
Low. The relevant commits have been in upstream
** Description changed:
== SRU Justification ==
- The update to stable 4.4.169 contains a couple of x86/kvm related
+ The update to stable 4.4.168 contains a couple of x86/kvm related
commits that have later fixup commits in upstream.
== Fix ==
Cherry-pick or backport the relevant
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
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/1811646
Title:
x86/kvm: Backport fixup comm
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
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/1811647
Title:
Xenial update: 4.4.170 upstr
** Summary changed:
- x86/kvm: Backport fixup commits
+ x86/kvm: Backport fixups and bugfixes
** Summary changed:
- x86/kvm: Backport fixups and bugfixes
+ x86/kvm: Backport fixup and missing commits
** Description changed:
== SRU Justification ==
The update to stable 4.4.168 contai
The following already present commits are incomplete and need fixing:
* KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
* x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
The modifications from the following patches are already present (from previous
SAUCE/embargoed patches):
* x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest
* x86/bugs, KVM: Support the combination of guest and host IBRS
--
You received this bug notification because you are a member of Kern
401 - 500 of 3121 matches
Mail list logo
