Hi Po-Hsu Lin,
Sorry for not updating this bug earlier.
Upstream 4.4 and 4.9 are also effected by this bug, so I went and posted the
patches to be considered for upstream -stable.
Upstream 4.4 thread: [1]
Upstream 4.9 thread: [2]
Now, I got some feedback from the original author of the upstream
ded => High
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Matthew Ru
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Disco)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
: 4e35c1cb9460240e983a01745b5f29fe3a4d8e39
Note the difference, old commit must be reverted first.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects
been proven in production
environments, so the overall risk is low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1836971
[Impact]
On machines with extremely high CPU usage, parent task groups which have
a large number of children can make the for loop in
sched_cfs_period_timer() run until the watchdog fires when the
cfs_period
Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => M
I have submitted the patch upstream to dri-devel and CC'd the hibmc
maintainers.
We will see where the discussion goes.
https://lists.freedesktop.org/archives/dri-devel/2019-August/231284.html
https://lists.freedesktop.org/archives/dri-devel/2019-August/231285.html
--
You received this bug noti
Hello @johannes-wuerbach
Thanks for the suggestion. I had a look at the patch you suggested:
commit 2181e455612a8db2761eabbf126640552a451e96
Author: Anton Eidelman
Date: Thu Jun 20 08:48:10 2019 +0200
subject: nvme: fix possible io failures when removing multipathed ns
The patch was backporte
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/
[Impact]
In environments which have CHECKSUM iptables rules set, the following
kernel call trace will be created when a GSO skb is processed by the
CHECKSUM target:
WARNING: CPU: 34 PID: 806048 at
/build/linux-zdslHp/linux-4.4.0/ne
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
- BugLi
x (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: Fix Committed
** Tags: sts verification-done-bionic
** Description changed:
- BugLink: https://bugs.launchpad.net/bugs/
+
The customer installed 4.15.0-59 from -proposed to a machine with
Mellanox Ethernet CX4LX cards, using the mlx5_core kernel module.
Checksums are now calculated correctly and the kernel spat does not
occur when the devices are brought up.
Marking this as verified.
** Tags added: verification-don
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1840619
[Impact]
In environments which have CHECKSUM iptables rules set, the following
kernel call trace will be created when a GSO skb is processed by the
CHECKSUM target:
WARNING: CPU: 34 PID: 806048 at
/build
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1840619
[Impact]
In environments which have CHECKSUM iptables rules set, the following
kernel call trace will be created when a GSO skb is processed by the
CHECKSUM target:
WARNING: CPU: 34 PID: 806048 at
/build
I have received confirmation from AWS that the fix for this issue has been
deployed to all commercial regions.
I have tested multiple VMs over the last few days and detaching EBS volumes are
working without problems.
This issue is now resolved.
** Changed in: linux (Ubuntu)
Status: Incomp
le a
fairly core part of the kernel, the changes are small and are focused on
the 0 condition.
In case of regression, simply revert all three offending commits.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Medium
https://launchpad.net/~mruffell/+archive/ubuntu/sf228435-test-generic
linux-image-aws: https://launchpad.net/~mruffell/+archive/ubuntu/sf228435-test
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Ass
of the NVMe driver, I believe there will be no regressions.
If you are interested in testing, I have prepared two ppas with
ef2d4615c59efb312e531a5e949970f37ca1c841 patched:
linux-image-generic:
https://launchpad.net/~mruffell/+archive/ubuntu/sf228435-test-generic
linux-image-aws:
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1833319
[Impact]
When copying files from a mounted LVM snapshot which resides on NVMe storage
devices, there is a massive performance degradation in the rate sectors are
read from the disk.
The kernel is not merging s
I tested a fully up to date cosmic VM using the reproducer steps in the
description, and found that I could not create a geneve tunnel when ipv6
is disabled.
I compiled a new cosmic kernel off the master-next branch with this commit
included:
"geneve: correctly handle ipv6.disable module paramete
I installed 4.15.0-56-generic to a bionic VM, with the -modules and
-modules-extra packages. I went into /var/lib/modules/4.15.0-56/ and did a
search for
hibmc_drm. There was no mention apart from a header Makefile. The module was not
built and not present on amd64.
I did the same for 5.0.0-22-g
I installed 4.15.0-56 from -proposed and ran some CPU stress tests and
everything was stable and no problems detected.
The kernel was also installed onto a few machines from the production hadoop
cluster which experienced extremely high cpu load, and the kernel is stable,
with
no CPU lockups in s
I installed 4.15.0-56-generic #62~16.04.1-Ubuntu xenial HWE kernel, and
I followed the reproducer instructions at https://github.com/brb/conntrack-race,
specifically loading in the NAT iptables rules, enabling debug output of the
conntrack file and running the programs server and client.
Looking
I installed linux-hwe 4.15.0-57 #63~16.04.1-Ubuntu on xenial, placed a
heavy load on the system.
Everything seemed stable and no lockups occurred. Due to the successful
tests in the hadoop environment under bionic and the nature of this
patch being from upstream stable, I am happy to mark this as
I installed linux-hwe 4.15.0-57 #63~16.04.1-Ubuntu on xenial, and
ensured the -modules and -modules-extra package was installed.
I went into /var/lib/modules/4.15.0-56/ and did a search for hibmc_drm.
There was no mention apart from a header Makefile. The module was not
built and not present on am
I installed linux-hwe 4.15.0-57 #63~16.04.1-Ubuntu on xenial.
I have run the reproducers on both bionic and xenial, and both have
positive results. This has been tested in the kubernetes environment
which had issues, and is performing well.
I am happy to mark this as verified for xenial.
** Tags
Hi Mohammad,
Can you please test the 4.15.0-88-generic kernel in -proposed again? The
SRU cycle will end in the next few days, and this bug needs to be
verified if at all possible.
To the kernel team:
The two commits:
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding
net/mlx5e: Rx,
I cannot reproduce this. I compiled the reproducer program and tested on
a Eoan VM running in KVM, with the same 5.3.0-29-generic kernel:
ubuntu@ubuntu:~$ ./socktest
Segmentation fault (core dumped)
ubuntu@ubuntu:~$ tail /var/log/kern.log
Feb 14 04:00:41 ubuntu kernel: [ 134.951620] socktest[159
cal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
If process that listens socket on any p
The regression was introduced by the following commit:
commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03
Author: Paul Wise
Date: Fri Aug 2 21:49:05 2019 -0700
Subject: coredump: split pipe command whitespace before expanding template
You can read it here:
https://github.com/torvalds/linux/commi
Hi Mohammad,
Thanks for verifying the kernel again, and good to see that things have
been fixed when you run padded traffic over your NICs.
The SRU cycle has completed, and the 4.15.0-88-generic kernel has been
released to -updates. You can go ahead and tell your affected customers
to upgrade to
I created a new c5d.large instance on AWS, and installed
4.4.0-177-generic from -updates. I ran through the reproduction steps,
and the issue reproduces.
I then created a new c5d.large instance, enabled -proposed and installed
4.4.0-178-generic. I again ran through the reproduction steps, and this
Hi Jens,
I highly recommend you go through the pain to upgrade the kernel on your
GPU cluster to something modern, like 4.15.0-91-generic. There was quite
a few regressions around the 4.15.0-56 to 4.15.0-58 mark, as we merged a
lot of upstream stable patches in at that time.
4.15.0-91 is pretty s
us: Fix Released
** Affects: kmod (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Desc
Attached is a picture of the garbled screen when VGA=std under booting
via kernel EFI stub.
** Attachment added: "Garbled screen"
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1872863/+attachment/5354248/+files/Screenshot%20from%202020-04-15%2012-19-48.png
--
You received this bug noti
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1872863
[Impact]
A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
kernel EFI stub whenever EFI is enabled. This causes problems for
QEMU/KVM virtual machines which use the VGA=std video device, a
Submitted Kernel patches to mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-April/109027.html
https://lists.ubuntu.com/archives/kernel-team/2020-April/109028.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Attached is the debdiff for kmod, which removes bochs-drm from the
framebuffer blacklist.
** Patch added: "kmod debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1872863/+attachment/5354280/+files/lp1872863_bionic.debdiff
--
You received this bug notification because yo
I rebuilt the kmod and Linux packages to include the ppc64le and powerpc
architectures, so we can test against POWER to ensure that LP #1378648
is no more, and we don't cause any regressions.
I don't have access to any POWER machines though, so I need help
testing.
--
You received this bug notif
Sudip Mukherjee made a more elegant fix than I did, and he posted it to
the fsdevel mailing list:
https://lore.kernel.org/linux-
fsdevel/20200416194612.21418-1-sudipm.mukher...@gmail.com/
I got an email saying that this has now been pulled into the -mm tree.
I will update when this patch reaches
I repeated the same SRU verification as before, this time using kmod
from -proposed.
I installed a fresh Bionic KVM, with EFI enabled. I upgraded the system
to use the latest -updates packages. Linux 4.15.0-99-generic and Kmod
24-1ubuntu3.3 were installed. I shut the machine down, set the VGA
devi
I went and looked at the autopkgtest regressions, and they aren't actual
regressions, just transient network problems and slow build timeouts.
chrony autopkgtest regression on armhf:
Need to get 263 kB of archives.
After this operation, 2,048 B of additional disk space will be used.
Err:1 http://
Hi Elvis, Guilherme
Guilherme, I went and had a look at what was built into
5.4.0-39-generic, and the commit "nfs: fix NULL deference in
nfs4_get_valid_delegation" wasn't there.
>From what I can see looking at the git tree located at:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/
Hi Elvis, excellent to hear your long production job finishes
successfully on your test kernel and on 5.4.0-40 from -proposed.
Looking at the schedule, 5.4.0-40 should be released to -updates in the
next day or two, and it will be exactly the same package that was in
-proposed. I'll mark this bug
Attached is screenshot proof that bochs-drm functions correctly on
4.15.0-96-generic ppc64el, and does not cause any regressions when
bochs-drm is enabled on ppc64el.
** Attachment added: "bochs-drm functions correctly on ppc64el"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+a
I have verified that enabling the bochs-drm kernel module on bionic does
not cause any regressions for PowerKVM machines when the video device is
VGA=std.
TLDR: See Screenshot:
https://launchpadlibrarian.net/475658598/Screenshot%20from%202020-04-22%2015-14-13.png
This is in response to the main c
Attached is proof the VM is using VGA=std for the ppc64el test.
** Attachment added: "Proof VM is running VGA=std on ppc64el"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+attachment/5357796/+files/Screenshot%20from%202020-04-22%2015-14-04.png
--
You received this bug notific
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1872863
[Impact]
A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
kernel EFI stub whenever EFI is enabled. This causes problems for
QEMU/KVM virtual machines which use the VGA=std video device, a
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1872863
[Impact]
A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
kernel EFI stub whenever EFI is enabled. This causes problems for
QEMU/KVM virtual machines which use the VGA=std video device, a
Sudip's commit landed in mainline last week, in time for 5.7-rc3:
commit db973a7289dad24e6c017dcedc6aee886579dc3a
Author: Sudip Mukherjee
Date: Mon Apr 20 18:14:20 2020 -0700
Subject: coredump: fix null pointer dereference on coredump
As of this morning, it has been queued up in Greg-KH's upst
For both tests I used the kmod package from my test ppa, since it is still
in the unapproved upload queue.
Firstly, I installed 4.15.0-99-generic from -updates, and booted my EFI based
KVM machine with VGA=std. The screen was garbled, as the framebuffer used was
efifb.
I then installed 4.15.0-100
The commit has landed in 5.3.0-56-generic on eoan and 5.4.0-38-generic
on focal, currently in -proposed.
Verification for each kernel:
I set the sysctl kernel.core_pattern to "|" with:
$ sudo sysctl kernel.core_pattern="|"
I then compiled the following reproducer:
int main()
{
*(int*)33 =
don't think
it will cause any regressions.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Xenial)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1882478
[Impact]
Intel Skylake server processors and onward have a different Last Level
Cache (LLC) topology than earlier processors, and such processors have a
new feature called Sub-NUMA-Clustering (SNC) which is si
Public bug reported:
[Impact]
I have a Logitech H340 USB Headset and a Logitech C270 Webcam I use for
meetings.
I access Google Meet with Firefox.
During a meeting, or immediately after one, and especially so if I join
a second meeting after one finishes, my input devices start acting up
and my
Attached is lsusb -vvv
** Attachment added: "lsusb -vvv"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329623/+files/lsusb.txt
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Med
Attached is syslog from jorunalctl --since today
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329622/+files/syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Attached is dmesg for 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31
20:24:34 UTC 2020
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329621/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages,
** Summary changed:
- Logitech USB Headset Causes Softlockups During Meetings
+ snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
I managed to figure out what was going on, and made a patch to fix the
problem. I sent it upstream for feedback:
Cover Letter:
https://lore.kernel.org/linux-fsdevel/20200220051015.14971-1-matthew.ruff...@canonical.com/
Patch:
https://lore.kernel.org/linux-fsdevel/20200220051015.14971-2-matthew.ru
*** This bug is a duplicate of bug 1864586 ***
https://bugs.launchpad.net/bugs/1864586
Hi Jonathan,
Thanks for reporting! This is an issue where the necessary files for the
new plymouth theme, plymouth-theme-spinner / bgrt, are not placed in
initrd properly. We are tracking this in Bug 186458
Hi Frank,
Just giving you an update on the status of these bugs. The kernel team
has reviewed the patches I submitted, and each set of patches have
received two acks each, meaning they will be built into the next kernel
update.
Bug 1842037:
https://lists.ubuntu.com/archives/kernel-team/2019-Octo
*** This bug is a duplicate of bug 1840854 ***
https://bugs.launchpad.net/bugs/1840854
Hello,
I believe this bug is a duplicate of Bug 1840854, and the fix should be
released in 4.15.0-59. Can you please review Bug 1840854 and try
installing a newer kernel, say 4.15.0-69, and let me know if i
@gunnarl, did your audio work correctly in kernel 5.0.0-29, and broke when you
updated to 5.0.0-31?
If you boot 5.0.0-29 by selecting it in grub when you turn your computer on,
does your audio work?
Might this be related to Bug 1846991?
--
You received this bug notification because you are a m
added: seg
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Hi Mohammad,
I have backported:
Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding
Commit: 0aa1d18615c163f92935b806dcaff9157645233a
to the bionic 4.15 kernel: https://paste.ubuntu.com/p/Svfp8DQGRP/
The test kernel is currently building in:
https://launchpad.net/~mruffell/+
Hi Mohammad,
I have completed backporting both commits and I have built test kernels
for each.
Can you install the test kernels and run the reproducer with Mellanox hardware?
My lab doesn't have any Mellanox NICs, so I can't test myself.
Please note these test kernels are NOT SUPPORTED by Canoni
** Description changed:
- Hi,
- we have the following issue which affects a lot of our customers this issue
fixes upstream and need to add the fixes to ubuntu 18.04.
+ BugLink: https://bugs.launchpad.net/bugs/1854842
- Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel
- Ubuntu
Hi Mohammad,
Thanks for testing those kernels.
The second one did not include 0aa1d18615c163f92935b806dcaff9157645233a,
which is why you still see the splat. Re-reading it,
db849faa9bef993a1379dc510623f750a72fa7ce depends on
0aa1d18615c163f92935b806dcaff9157645233a to function, and I probably
sho
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
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/1842037
Title:
SUNRPC: Use after free when GSSD credentia
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
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/1828978
Title:
NFSv4.1: Interrupted connections cause hig
Hi Frank,
Thanks for testing the kernel in -proposed, it lets us mark the bug as
verified so the patches make it into the release, which will be
happening in about two weeks going by https://kernel.ubuntu.com/
Just to be clear, you tested the bionic-hwe kernel 5.0.0-37~18.04.1 from
bionic -propos
Hi @mohamadh,
Are you using the in-tree drivers that Ubuntu supplies?
I have seen some customers using out of tree MOFED drivers from the
Mellanox website that have been out of date, and being able to reproduce
this on newer kernels like 4.15.0-66. Upon updating to newer MOFED
drivers or revertin
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug noti
Hi Frank,
I have good news. The SRU has finished and the kernel update has been
released to -updates. You can "apt update" and "apt upgrade" to install
the fixed kernel.
This kernel should be the exact same as the one from -proposed, which is
version 5.0.0-37.40~18.04.1, so if you are still runni
m
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: linux (Ubuntu Eoan)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/
[Impact]
There is a problem where kernels 5.0-rc1 and onwards cannot mount a
multi tier cifs DFS setup, while kernels 4.20 and below can mount the
share fine.
The DFS tiering structure looks like this:
Doma
Hi Mohammad,
It seems things have returned back to normal for this current SRU cycle,
and the two commits you requested:
net/mlx5e: Rx, Fix checksum calculation for new hardware
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding
Have been tagged and built into the 4.15.0-87-generic
Verification for eoan, via the Bionic 5.3 HWE kernel. The customer
installed 5.3.0-40-generic #32~18.04.1-Ubuntu to their bionic machine,
and mounted their multi-tier cifs share:
@:~$ uname -rv
5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020
@:~$ cd /mnt/share/
@:/mnt/share$ ll
Hi Mohammad,
Can you double check that you tested with the 4.15.0-87-generic kernel
from -proposed with the following uname string?
4.15.0-87-generic #87-Ubuntu SMP Fri Jan 31 19:32:37 UTC 2020
You can verify that the patches have landed in the kernel by looking at
the git tree:
Checkout the co
Hi Frank,
It has been 9 days, or slightly over a week since you applied the respun
test kernel to your systems.
Are your systems stable now? Are they suffering any symptoms of Bug
1842037 or Bug 1828978?
Is the test kernel more stable than regular released Ubuntu kernels? Do
you think the patche
** Summary changed:
- NFS connections block while causing a high-bandwidth RPC-pingpong between
client and server
+ NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between
client and server
** Description changed:
- There's a bug in kernels before Linux 5.0 that affects NFS
** Summary changed:
- Oops when Kerberos credentials are invalid
+ SUNRPC: Use after free when GSSD credentials are invalid causes oops
** Description changed:
- There's a bug in Linux Kernel 5.0 which is triggered by invalid
- credentials when the NFS clients is trying to aquire them via GSSD.
Hi Frank,
Great to hear that the respun test kernel solves your NFS issues.
I have submitted the patches to be included in the Ubuntu Bionic 5.0 HWE
kernel.
You can see the patches on the kernel mailing list if you are
interested:
Bug 1842037:
https://lists.ubuntu.com/archives/kernel-team/2019
Hello Mohammad,
The kernel team has reviewed the patches and they have received two acks
from senior kernel developers:
https://lists.ubuntu.com/archives/kernel-team/2019-December/106516.html
https://lists.ubuntu.com/archives/kernel-team/2020-January/106624.html
>From there, the patch was applie
Verification for the revert:
lab@hostname:~$ uname -a
Linux hostname 4.15.0-75-generic #85-Ubuntu SMP Wed Jan 15 00:31:23 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
lab@hostname:~$ dmesg | grep "Cannot enable"
lab@hostname:~$ dmesg | grep "Maybe"
lab@hostname:~$
Booting the bionic kernel 4.15.0-75-
Verification for disco. I went and installed 5.0.0-40-generic from -proposed
to a disco box:
$ uname -rv
5.0.0-40-generic #44-Ubuntu SMP Wed Jan 15 02:03:45 UTC 2020
I do not have access to a multi tier cifs mount, so I will try and
connect to a known one with a bad username / password to ensure
Hi Mohammad,
I have some bad news. The patches are not present in the current SRU
cycle and have been delayed until the next SRU cycle.
This is not unique to us and this LP bug, everyone has had the same
thing happen to them.
The reason is that the kernel team are currently spinning kernels for
I enabled enabled -proposed and installed 4.4.0-155.182, and went through the
test case on a c5.large instance on aws. Note, I used the -generic kernel since
-aws doesn't seem to be ready yet.
The problem is solved and performance is the same as non-snapshot
mounted disks.
We can see that merging
I enabled -proposed and installed 4.4.0-1088-aws #99-Ubuntu, and again
went through the test case on a c5.large instance on aws.
The problem is solved and performance is restored, and performs the same
as a non-snapshot mounted disk.
Again, we can see merging has been enabled with:
$ cat /sys/bl
This was released in 4.15.0-59-generic and works as intended. Marking
Fix Released. Note, this still needs to land in linux-gcp for Bionic due
to some technical reasons.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification becaus
sco)
Status: New => Invalid
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** No longer
I installed 4.4.0-163-generic from xenial -proposed to a xenial VM, with
the following uname -rv:
4.4.0-163-generic #191-Ubuntu SMP Wed Sep 11 17:06:27 UTC 2019
>From there I enabled a iptsables rule with the CHECKSUM target, for tcp
port 8000:
sudo iptables -t mangle -A POSTROUTING -p tcp -m tc
Hi Frank,
Thanks for the update. Let me know how the test kernel goes when users
are on the system.
I looked into your stack trace and found the below link:
https://lore.kernel.org/lkml/20190529151003.hzmesyoiopnbc...@aura.draconx.ca/T/
I'm sure you have probably found it too when researching t
Hi Benjamin,
I have good news. The SRU has completed, and the new kernels have now
been released to -updates. Their versions are:
Bionic:
4.15.0-126-generic
Focal:
5.4.0-56-generic
You can go ahead and schedule that maintenance window now, to install
the latest kernel from -updates. These kerne
Hi Thimo,
Thank you for the very detailed bug report. I will start investigating this
immediately.
Thanks,
Matthew
--
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/1907262
Title:
raid10:
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Stat
Hi Thimo,
Firstly, thank you for your bug report, we really, really appreciate it.
You are correct, the recent raid10 patches appear to cause filesystem
corruption on raid10 arrays.
I have spent the day reproducing, and I can confirm that the
4.15.0-126-generic, 5.4.0-56-generic and 5.8.0-31-gen
Hi Markus,
I am deeply sorry for causing the regression. We are aware, and tracking
the issue in bug 1907262.
The kernel team have started an emergency revert and you can expect
fixed kernels to be released in the next day or so.
--
You received this bug notification because you are a member of
1 - 100 of 531 matches
Mail list logo
