Public bug reported:
Tons of the following in the log on 17.10:
Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion
'str_array != NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion
'member_name != NULL' failed
Nov 15 07:49:08 gollum
Public bug reported:
Cloning a uvt VM fails with error: Unknown driver 'iso'
To reproduce:
uvt-simplestreams-libvirt sync release=xenial arch=amd64
uvt-kvm create test-vm release=xenial arch=amd64
virsh destroy test-vm
virt-clone -o test-vm -n cloned-vm --auto-clone
Which results in:
WARNING
Upsttream fix: https://www.redhat.com/archives/libvir-
list/2017-March/msg00259.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729858
Title:
virt-clone fails with: Unknown driver 'iso'
To
Backported and tested patch attached.
** Patch added: "0001-storage-Don-t-pass-iso-format-to-qemu-img.patch"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1729858/+attachment/5003020/+files/0001-storage-Don-t-pass-iso-format-to-qemu-img.patch
--
You received this bug notification
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
** 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
** 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 Ubuntu
Bugs, which is subscribed to 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).
+ Change flush method from
** Description changed:
- Upstream's Spectre v1 mitigation prevents speculation on a user
- controlled pointer. This part of the Spectre v1 patchset was never
- backported to 4.4 (for unknown reasons) so Xenial is lacking it as well.
- All the other stable upstream kernels include it, so add it
** 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
List of previously applied patches:
* mac80211_hwsim: fix possible memory leak in hwsim_new_radio_nl()
* bpf: fix selftests/bpf test_kmod.sh failure when CONFIG_BPF_JIT_ALWAYS_ON=y
* virtio-net: Fix operstate for virtio when no VIRTIO_NET_F_STATUS
--
You received this bug notification
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 already-applied patches:
* Input: elan_i2c - add ELAN0612 (Lenovo v330 14IKB) ACPI ID (applied as:
UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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
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
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+
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
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
List of previously applied patches:
* Revert "ima: limit file hash setting by user to fix and log modes"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776177
Title:
Xenial update to 4.4.136
Thanks for the clarification, @brenohl. I decided to drop the two and
adjust the patch that collided. See https://lists.ubuntu.com/archives
/kernel-team/2018-May/092834.html.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For the latest xenial patchset: What's the purpose of patches 0001 &
0004??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744173
Title:
rfi-flush: Switch to new linear fallback flush
To manage
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
Public bug reported:
Upstream's Spectre v1 mitigation prevents speculation on a user
controlled pointer. This part of the Spectre v1 patchset was never
backported to 4.4 (for unknown reasons) so Xenial is lacking it as well.
All the other stable upstream kernels include it, so add it to Xenial.
** Summary changed:
- Add array_index_nospec
+ Update to upstream's implementation of Spectre v1 mitigation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774181
Title:
Update to upstream's
** Description changed:
Xenial is currently lacking full support of upstream's Spectre v1
- mitigation. As a first step to get there, add the array_index_nospec
- macro and all the (simple) patches that make use of it.
+ mitigation. Add the missing patches and merge them with Ubuntu's current
+
Skipped the following patches (already applied):
* KVM: s390: Enable all facility bits that are known good for passthrough
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774173
Title:
Xenial
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1772671
Title:
Kernel produces empty lines in /proc/PID/status
To
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1772575
Title:
Kernel 4.4 NBD size overflow with image size exceeding
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1772775
Title:
4.4.0-127.153 generates many "sit: non-ECT" messages
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773905
Title:
Support UVC1.5 Camera for Xenial
To manage notifications
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1771301
Title:
Setting ipv6.disable=1 prevents both IPv4 and IPv6
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1771826
Title:
Creation of IMA file hashes fails when appraisal is
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1744173
Title:
rfi-flush: Switch to new linear fallback flush
To
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
Public bug reported:
Xenial is currently lacking full support of upstream's Spectre v1
mitigation. As a first step to get there, add the array_index_nospec
macro and all the (simple) patches that make use of it.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Juerg Haefliger
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765007
Title:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767857
Title:
Kernel 4.4.0-122 Breaks qemu-system-x86
To man
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
** 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768429
Title:
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
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
*** 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
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
Verified that the new package fixes the issue.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696710
Title:
Skipped the following patch (already applied):
* KVM: s390: wire up bpb feature
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768474
Title:
Xenial update to 4.4.130 stable release
To manage
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
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Hmm... Why do you think this is a duplicate of #1720159? My stack trace
looks different.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed, 110 doesn't load microcode on my old laptop.
$ cat /proc/cpuinfo | grep -m1 'model name'
model name : AMD E1-1200 APU with Radeon(tm) HD Graphics
$ uname -a
Linux cq58 4.4.0-110-generic #133-Ubuntu SMP Fri Jan 12 18:53:57 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774181
Title:
Update to upstream's implementation of Spectre v1
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775137
Title:
Prevent speculation on user controlled pointer
To
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
Per git bisect, the fix for this should be:
commit 6c971c09f38704513c426ba6515f22fb3d6c87d5
Author: Y.C. Chen
Date: Thu Jan 26 09:45:40 2017 +0800
drm/ast: Fixed system hanged if disable P2A
The original ast driver will access some BMC configuration through P2A
bridge
that
Public bug reported:
Booting Trusty with kernel 3.13.0-156-generic on a fairly new Intel box
results in stuck CPU warnings:
[ 33.551942] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:1119]
[ 33.558560] Modules linked in: hid_generic ast(+) crct10dif_pclmul
syscopyarea crc32_pclmul
eam update)
+ and received testing there.
+
+ == Test Case ==
+
+ Booted a patched kernel on HW to verify it comes up without stuck CPU
+ warnings.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member o
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774181
Title:
Update to upstream's implementation of Spectre v1
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775137
Title:
Prevent speculation on user controlled pointer
To
Public bug reported:
== SRU Justification ==
Booting Trusty with kernel 3.13.0-156-generic on a fairly new Intel box
with a i40e NIC results in no network. The 3.13 i40e driver doesn't
support the following HW:
3d:00.0 Ethernet controller: Intel Corporation Device 37d2 (rev 02)
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780062
Title:
Cloud-init causes potentially huge boot delays
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ SRU Justification
- 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
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
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755509
Title:
Xenial update to 4.4.115 stable release
To manage notifications about this
** 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 a
** 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 a
** 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
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
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756121
Title:
Xenial update to 4.4.116 stable release
To manage notifications about this
Skipped the following patches (previously applied already):
* bpf: fix branch pruning logic
* loop: fix concurrent lo_open/lo_release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755509
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755817
Title:
Segmentation fault in ldt_gdt_64
To man
y: Jiri Slaby <jsl...@suse.cz>
+ (cherry picked from commit 62fc7228f8cc8c89ecbd37008a0495ac28e41c5c)
+ Signed-off-by: Juerg Haefliger <juerg.haefli...@canonical.com>
+ Signed-off-by: Stefan Bader <stefan.ba...@canonical.com>
--
You received this bug notification beca
471bd865b318db34c7b628.1438291540.git.l...@kernel.org
Signed-off-by: Ingo Molnar <mi...@kernel.org>
Signed-off-by: Jiri Slaby <jsl...@suse.cz>
(cherry picked from commit 62fc7228f8cc8c89ecbd37008a0495ac28e41c5c)
Signed-off-by: Juerg Haefliger <juerg.haefli...@canonical.com
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756866
Title:
Xenial update to 4.4.118 stable release
To manage notifications about 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 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
Skipping the following patches (already applied):
* KVM: VMX: Make indirect call speculation safe
* KVM: x86: Make indirect calls in emulator speculation safe
* Drivers: hv: vmbus: fix build warning
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Skipping the following patches:
* x86/kvm: Update spectre-v1 mitigation
* x86/spectre: Report get_user mitigation for spectre_v1
* nl80211: Sanitize array index in parse_txq_params
* vfs, fdtable: Prevent bounds-check bypass via speculative execution
* x86/syscall: Sanitize syscall
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 patches because they were applied already:
* netfilter: x_tables: pack percpu counter allocations
* netfilter: x_tables: pass xt_counters struct to counter allocator
* netfilter: x_tables: pass xt_counters struct instead of packet counter
* ARM: omap2: hide
** 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
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 patches because they're applied already:
* bpf: fix incorrect sign extension in check_alu_op()
* scsi: ses: don't get power status of SES device slot on probe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Skipped the following commit since it introduces a build failure as shown below:
* perf tests: Decompress kernel module before objdump
CC tests/llvm-src-base.o
CC tests/llvm-src-kbuild.o
LD util/libperf-in.o
tests/code-reading.c: In function 'read_object_code':
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 because they modify upstream's Spectre v1 code
which we haven't pulled in (yet) with the 4.4.118 stable update:
* nospec: Kill array_index_nospec_mask_check()
* nospec: Move array_index_nospec() parameter checking into separate macro
--
You received this bug
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 because they're already applied:
* scsi: libiscsi: Allow sd_shutdown on bad transport
* blk-mq: NVMe 512B/4K+T10 DIF/DIX format returns I/O error on dd with split
op
--
You received this bug notification because you are a member of Ubuntu
Bugs, 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 from a mainline/stable
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
** Changed in: linux (Ubuntu)
Status: New => Invalid
** 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
Reverted the following SAUCE patch to be replaced by its upstream equivalent:
* UBUNTU: SAUCE: (no-up) iio: st_pressure: st_accel: Initialise sensor
platform data properly
Skipped the following patches since they're already applied:
* CIFS: Enable encryption during session setup phase
*
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
** 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
Skipped the following patch:
* x86/syscall: Sanitize syscall table de-references under speculation fix
Which fixes a Spectre v1 commit from upstream 4.4.118 which we haven't
applied (yet).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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 patch:
* mpls, nospec: Sanitize array index in mpls_label_ok()
It references array_index_nospec() which comes from upstream's Spectre
v1 implementation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
201 - 300 of 1814 matches
Mail list logo
