Sorry for the confusion. Thank you for clarifying. Here is our test:
We installed linux-5.4.0-156.173 (focal) from -proposed and tested it out with
good results. Ran test script on a mounted nfs share. Silly little test
(test.sh seen below):
#!/bin/bash
nfsstat -l | grep access
touch myfiles.
Hello @ihmesa,
We cannot release linux-5.4.0-154.171 anymore, it has been replaced in
-proposed by linux-5.4.0-156.173 which also contains the same fix. We
would appreciate if you could help us test the fix from this version in
-proposed.
Thank you.
--
You received this bug notification because
According to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098, a patched
gke kernel was released to revert the default behavior and add the
nfs_fasc module parameter. linux-5.4.0-154.171 was proposed, but not
released. Can that be moved forward to fix this for impacted users?
--
You r
Hi @kleber-souza, @chengendu
Thanks for your attention.
Allow me give my perception of the impact of fixing "bug" LP: #2003053.
The original patchset introduced *two* regressions. One, (NFS deathlock)
that hit everybody - fixed by #2009325, but the remaining one, are now
hitting those of use spa
** Tags added: patch
--
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/2015827
Title:
NFS performance issue while clearing the file access cache upon login
Status in linux package in Ubunt
The NFS patchset did resolve the issue our user encountered, but unfortunately
introduced some performance overhead that may have significant impacts in
certain scenarios.
We wanted to let you know that we have submitted a patch
(https://patchwork.kernel.org/project/linux-nfs/patch/2023041103024
Hello @kleber-souza.
The regression was not fixed. There have only been mitigations.
Please see our comments in the other bug report.
All information required is available in the previous bug report, but I
have attached a patchset that actually fixes the regression.
** Patch added: "Reverts up
Hello @jan-launchpad-xud and @soeby.
The patches we introduced to fix bug 2003053 unfortunately introduced a
regression that was not caught by our tests and the reviews done
internally and by upstream. The regression was fixed as soon as we could
and we apologize for the inconvenience. We do have
Judging from the utter lack of response to the core issue of backporting
untested patches from an - at the time - release candidate unstable
upstream Linux version, back to what is supposed to be *three* long term
support "enterprise grade" Ubuntu editions, it seems that Ubuntu's
policy for Linux k
Du ChengEn, I would second Jan's opinion.
This whole chain of fixes that has gone in to fix LP: #2003053, should
be rolled back. There where no heavy arguments to cherry-pick those
changes in the first place. (It is not in upstream LTS either).
Once it was discovered what kind of impact it had, i
Please note that this is a bug that for unknown reasons have been
backported from 6.2-rc3 to LTS released kernels in Ubuntu Server LTS.
Upstream is not responsible for making the decision of whether this
backported change should be part of older kernels in Ubuntu Server LTS.
Please revert the cha
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => ChengEn, Du (chengendu)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
12 matches
Mail list logo
