This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 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-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-azure/6.2.0-1009.9
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-lunar' to 'verification-done-lunar'. If the
problem still exists,
Hi,
I can also confirm that kernel 5.4.0-149.166 brings CPU on the 20.04.6
NFS server back from 90-100% to normal, but i observed the following.
After reboot of the NFS server all CPU are going quickly to 100% load,
to get load back to normal I had to do a `exportfs -ra' else CPU stays
even with
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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-jammy' to 'verification-
done-jammy'. If the problem
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2009325
Title:
NFS deathlock with last Kernel
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1029.34~20.04.1 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-focal' to
'verification-done-focal'. If the
Sorry to bother, but unfortunately, I have difficulties to understand
the state of this bug.
As I understand from comment 55
https://bugs.launchpad.net/ubuntu/bionic/+source/linux/+bug/2009325/comments/55
The NFS bug is fixed with package
jammy/linux: 5.15.0-69.76
And the latest Ubuntu 22.04
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2009325
Title:
NFS deathlock with last Kernel
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1031.35~20.04.1 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-focal' to
'verification-done-focal'. If the problem
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
This bug is awaiting verification that the linux-bluefield/5.4.0-1061.67
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-focal' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1028.33 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-jammy' to 'verification-
done-jammy'. If the problem still
Judging from previous comments this change was verified.
Verification is requested again because the initial change was pushed in the
last cycle and non aws derivatives that were not respun introduced this change
in this cycle.
Since this is blocking the release of a lot of kernels for cycle
This bug was fixed in the package linux-aws - 6.2.0-1003.3
---
linux-aws (6.2.0-1003.3) lunar; urgency=medium
* lunar/linux-aws: 6.2.0-1003.3 -proposed tracker (LP: #2015430)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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-jammy' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-gke/5.4.0-1097.104
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-focal' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-
gcp-4.15/4.15.0-1148.164 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-bionic' to 'verification-
done-bionic'. If the problem still
This bug is awaiting verification that the linux-gkeop/5.4.0-1067.71
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-focal' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-ibm/5.19.0-1020.22
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-kinetic' to 'verification-done-kinetic'. If the
problem still
Hi @chengendu,
Thanks.
I have posted a comment to the effect of backporting changes in new (and
at the time, unreleased and not yet stable) Linux kernels to LTS
releases. There is no need to await upstream's feedback and judgment,
this change belongs to Linux 6.2, not old LTS kernels.
--
You
This bug is awaiting verification that the linux-kvm/5.19.0-1021.22
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-kinetic' to 'verification-done-kinetic'. If the
problem still
Hi @krglosse,
We have opened a bug to address the performance issue related to NFS.
You can find more details about the bug at this link:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827.
We have also sent a proposal to upstream for their consideration, but
unfortunately, we have
This bug is awaiting verification that the linux-gke/5.15.0-1031.36
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-
allwinner/5.19.0-1010.10 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-kinetic' to 'verification-
done-kinetic'. If the problem
This bug is awaiting verification that the linux-starfive/5.19.0-1015.17
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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-riscv/5.19.0-1016.17
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-kinetic' to 'verification-done-kinetic'. If the
problem still
Hi ChengEn, Du,
Do we have another issue opened to address the NFS mechanism and the
performance impacts it has on the kernel? We cannot move to the new
kernel currently because of these issues so I just want to make sure we
are continuing to push a solution forward. Thank you!
--
You received
This bug is awaiting verification that the linux-oracle/5.15.0-1033.39
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-jammy' to 'verification-done-jammy'. If the
problem still
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-bionic verification-done-focal
verification-done-jammy verification-done-kinetic
--
You received this bug notification because you are a
This bug is awaiting verification that the linux-ibm/5.15.0-1028.31
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-raspi2/4.15.0-1130.138
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-bionic' to 'verification-done-bionic'. If the
problem still
This bug is awaiting verification that the linux-oracle/4.15.0-1117.128
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-bionic' to 'verification-done-bionic'. If the
problem still
This bug is awaiting verification that the linux-gcp/5.19.0-1020.22
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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-ibm/5.4.0-1047.52
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-focal' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-gkeop/5.15.0-1018.23
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oracle/5.19.0-1020.23
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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-raspi/5.15.0-1027.29
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-raspi/5.4.0-1083.94
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-focal' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-kvm/4.15.0-1138.143
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-bionic' to 'verification-done-bionic'. If the
problem still
This bug was fixed in the package linux - 6.2.0-19.19
---
linux (6.2.0-19.19) lunar; urgency=medium
* lunar/linux: 6.2.0-19.19 -proposed tracker (LP: #2012488)
* Neuter signing tarballs (LP: #2012776)
- [Packaging] neuter the signing tarball
* LSM stacking and AppArmor
** Tags removed: verification-needed-bionic verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2009325
Title:
NFS deathlock with last Kernel 5.4.0-144.161 and
For Jammy
5.19.0-38-generic
and
5.15.0-70-generic
Fixed my problems with nfs client performance.
Thanks!
Should I change the tags the ubuntu-kernel-bot is talking about?
verification-needed-jammy to verification-done-jammy?
I'm assuming not but I wouldn't want to see this bug closed and the
This bug is awaiting verification that the linux-raspi/5.19.0-1016.23
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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-gcp/5.15.0-1032.40
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-kvm/5.4.0-1089.95
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-focal' to 'verification-done-focal'. If the
problem still exists,
we have tested on 5.4.0-1099-aws and this issue is fixed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2009325
Title:
NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-kvm/5.4.0-1089.95
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-focal' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-kvm/5.15.0-1031.36
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/4.15.0-1154.167
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-bionic' to 'verification-done-bionic'. If the
problem still
This bug is awaiting verification that the linux-gcp/5.15.0-1032.40
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-dell300x/4.15.0-1063.68
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-bionic' to 'verification-done-bionic'. If the
problem still
Hi Du ChengEn,
Thanks for you feedback, and understanding of our issue.
I will be watching the nfs mailing list as well, but kindly post
references to the bug here, once the bug is opened.
I support your idea, of a separate mount-option, if it is not possible
to address both issues.
Looking at
I would like to begin by expressing my sincere appreciation for your invaluable
assistance in identifying the performance issue and presenting us with a clear
reproducer for testing.
Your contributions have been extremely helpful.
We have carefully considered the possibility of reverting the
This bug is awaiting verification that the linux-aws/5.15.0-1034.38
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oracle/5.4.0-1099.108
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-focal' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-
azure-4.15/4.15.0-1163.178 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-bionic' to
'verification-done-bionic'. If the problem
This bug is awaiting verification that the linux-azure/5.15.0-1036.43
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.4.0-1106.112
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-focal' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.4.0-1100.108
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-focal' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-gcp/5.4.0-1103.112
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-focal' to 'verification-done-focal'. If the
problem still exists,
Hi Du ChengEn,
Is there a better place to track the fix to the overall problem with the
newer kernel? We needed to revert until we can get a more long term fix
in the newer kernel as the current fix does not fully address our
problem.
Thanks!
--
You received this bug notification because you
This bug is awaiting verification that the linux-azure/5.19.0-1023.24
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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1023.24
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-kinetic' to 'verification-done-kinetic'. If the
problem still
Hi Du ChengEn,
Thanks for the clarification on test kernels. I am sad, I did not get to
test your 2nd test kernel, as that would have revealed this issue
immediately.
While the changes to fix LP: #2003053, went in there to fix a "bug" - it
also created this major regression. But the bug fix just
Thanks again, but why is it not possible to roll back the NFS change and
roll out only the security relevant content in the meanwhile?
Nearly one month and counting for balancing the need for systems being
up vs. having security updates is not quite tenable for most system
administrators.
--
I apologize for any confusion that may have arisen.
The test kernel 5.15.0-67.74+test20230307b2h2cbb6062f8eb has completely
reverted the new mechanism, resulting in the same behavior as before.
We understand that this can be concerning, and we want to assure you that we
are actively working
Hi Du ChengEn,
Thanks for your efforts in making this change for this SRU cycle.
However, I can confirm that we too are facing challenges with orders of
magnitude (>10x) increases in ACCESS calls, with the newly released
kernels. Still better/differently than 5.15.0-67, but not suitable for
I think Ben's question could be clarified with:
How does "login" relate to non-login (non-interactive) processes started
automatically via system processes?
Our issue is with suexec-like mechanisms, and the 2 orders of magnitude
increase ACCESS and 1 order of magnitude for LOOKUP, while
Du ChengEn, thank-you for your additional comments. We are seeing good
behaviour after the patch.
However, (and please feel free to call me stupid) when you talk about user's
login time, how does this reflect with system processes, such as www-data
(apache2), or similar? Is a "login" for
Hi,
I would like to share my thoughts on the increase in LOOKUP operations, which
may be attributed to a new mechanism introduced in the Linux 6.2-rc3 NFS client
side.
This mechanism clears the access cache as soon as the cache timestamp becomes
older than the user's login time.
Its primary
While the operation rates are drastically improved compared to the
broken kernel, even with the the patched kernel 5.15.0-69.76 we're still
seeing a large increase in NFS ACCESS operations, up from about 90/s to
1500/s over a couple servers. Additionally, about a 5x increase in
LOOKUP operations
This bug was fixed in the package linux-aws - 4.15.0-1153.166
---
linux-aws (4.15.0-1153.166) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1153.166 -proposed tracker (LP: #2012003)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS:
This bug was fixed in the package linux - 4.15.0-208.220
---
linux (4.15.0-208.220) bionic; urgency=medium
* bionic/linux: 4.15.0-208.220 -proposed tracker (LP: #2012097)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
Confirming the proposed 5.4.0-1099 packages resolve the NFS bug on
Bionic running in AWS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2009325
Title:
NFS deathlock with last
Can confirm that 5.15.0-1033 seems to have resolved the NFS bug on Jammy
running on AWS.
Is there a timeframe for the same patch to be applied to the 5.19 kernel
train?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux-aws - 5.15.0-1033.37
---
linux-aws (5.15.0-1033.37) jammy; urgency=medium
* jammy/linux-aws: 5.15.0-1033.37 -proposed tracker (LP: #2011997)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux-aws - 5.4.0-1099.107
---
linux-aws (5.4.0-1099.107) focal; urgency=medium
* focal/linux-aws: 5.4.0-1099.107 -proposed tracker (LP: #2012000)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct
Even worse, is it even possible to downgrade? I couldn't see any viable
option via madison.
linux-image-aws | 5.15.0.1031.35~20.04.20 |
http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
linux-image-aws | 5.15.0.1031.35~20.04.20 | http://security.ubuntu.com/ubuntu
Thanks for the update @kleber-souza!
Would early next week be Monday/Tuesday or is it possible it bleeds into
Wednesday/Thursday morning/etc? We are also doing a risk assessment and
knowing this will greatly help our cause.
Thanks in advance!
--
You received this bug notification because you
Not only is it about severe loss of service, but this also keeps
numerous systems at risk because they cannot easily install a kernel
with the security fixes.
For the future, please consider not bundling security releases with
other fixes, as to avoid this situation where systems essentially
Why is this not recognised as critical? We identified this as a major
incident, with severe loss of service (availability) and likewise
opening a risk assessment in relation to our dependency on Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hello,
The Canonical Kernel Team is planning to release the affected kernels in
Jammy (22.04), Focal (20.04) and Bionic (18.04) early next week.
Thank you everyone for helping with tests and additional information.
--
You received this bug notification because you are a member of Kernel
@ChengEn, Du thank you for the quick fix commit!!
I was curious if ya'll had any idea on how long it will take this change
to specifically hit the focal and bionic linux releases?
And if not, do we have a general idea on how long this process usually
takes?
Thanks again!
--
You received this
Any idea when a new kernel package for Focal (20.04) will be made
available? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2009325
Title:
NFS deathlock with last Kernel
This bug was fixed in the package linux - 5.19.0-38.39
---
linux (5.19.0-38.39) kinetic; urgency=medium
* kinetic/linux: 5.19.0-38.39 -proposed tracker (LP: #2012088)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux-aws - 5.19.0-1022.23
---
linux-aws (5.19.0-1022.23) kinetic; urgency=medium
* kinetic/linux-aws: 5.19.0-1022.23 -proposed tracker (LP: #2011996)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS:
This seems to also affect the 5.19.0 kernel train as well (linux-aws-
edge on jammy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2009325
Title:
NFS deathlock with last Kernel
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-aws (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-aws (Ubuntu Focal)
Status: New => Fix
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Kinetic)
Status:
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Assignee: ChengEn, Du (chengendu)
Status: Confirmed
I've had this issue within AWS using:
linux-aws: 5.15.0-1031
linux-image-5.15.0-1031-aws
Problem goes away with linux-image-5.15.0-1030-aws
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
A problematic patch has been identified in a bug report, which can lead to
issues.
The bug report can be found at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053.
This patch can affect several kernels, including:
linux/4.15.0-206.217 for bionic
linux/5.4.0-144.161 for focal
And the nfs_access_add_cache function looks similar to 5.15.0 so the
same fix will probably work.
--
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/2009325
Title:
NFS deathlock with last
Hi,
I believe I have seen the same problem on 5.19.0-35-generic
It was not present on 5.19.0-32-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/2009325
Title:
NFS deathlock
Hello ChengEn, Du ,
I have tested also the 2nd.
Same as the previous test kernel , the 2nd (5.15.0-67-generic
#74+test20230308b0h1a13a615ee32-Ubuntu) seems to work as intended .
Same as Alexander , this patch seems to fix the problem.
Best regards,
--
You received this bug notification
Hello ChengEn, Du ,
Thanks for the test Kernel.
I can no longer find a problem with this Kernel and NFS client.
I also think that the kernel has fixed the problem.
Best regards,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => ChengEn, Du (chengendu)
--
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/2009325
Title:
NFS deathlock with last Kernel
1 - 100 of 114 matches
Mail list logo
