Thanks ruddk, it was a pleasure. We will let this bake in -proposed for
a few weeks, and then barring any unforeseen issues it will get promoted
to -updates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu 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/1509120
Title:
Process accounting deadlock with idmapd
--- Comment From ru...@us.ibm.com 2015-11-07 00:59 EDT---
Thanks. The updated 1:1.2.8-6ubuntu1.2 version of nfs-common did indeed pull
in the keyutils package. This was tested for both the ppc64el and amd64
architectures.
root@p824l:~# apt-show-versions nfs-common
Hello bugproxy, or anyone else affected,
Accepted nfs-utils into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/nfs-
utils/1:1.2.8-6ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Description changed:
[Impact]
* Programs accessing nfsv4 mounts will hang on request_key interface
with nfs4 + sec=sys with old nfsv4 hosts. Kernel is waiting on
usermodehelper provided by keyutils.
* INFO: task ls:2101 blocked for more than 120 seconds.
Not tainted
This dependency is already present in vivid and later.
** Also affects: nfs-utils (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: nfs-utils (Ubuntu Trusty)
Importance: Undecided =>
** Description changed:
[Impact]
- * Programs accessing nfsv4 mounts will hang on request_key interface
+ * Programs accessing nfsv4 mounts will hang on request_key interface
with nfs4 + sec=sys with old nfsv4 hosts. Kernel is waiting on
usermodehelper provided by keyutils.
- *
Yeah, I think so, if you are "creative" enough to put your accounting on
your nfs mount, and then have your nfs service fail, you should expect
your machine to stop functioning. Otherwise it could be a potential
accounting/security hole.
--
You received this bug notification because you are a
** Tags added: sts
--
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/1509120
Title:
Process accounting deadlock with idmapd callout when writing to NFSv4
mount
Status in linux package
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
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/1509120
Title:
Process accounting deadlock with
I verified that keyutils is already included in vivid+ in order to fix
1449074. So this shouldn't be too much of an issue to fix in trusty as
well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ [Impact]
+
+ * Programs accessing nfsv4 mounts will hang on request_key interface
+ with nfs4 + sec=sys with old nfsv4 hosts. Kernel is waiting on
+ usermodehelper provided by keyutils.
+
+ * INFO: task ls:2101 blocked for more than 120 seconds.
+ Not tainted
Add keyutils to Depends: for nfs-common
** Patch added: "lp1509120.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509120/+attachment/4512348/+files/lp1509120.trusty.debdiff
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) => Dave Chiluk (chiluk)
--
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/1509120
Title:
Process accounting deadlock with
I created a centos 6 nfsv4 server, and went through the above recreate
procedure with a trusty guest, and could successfully mount, and do file
operations with accton. However after a few minutes, the console hung,
and most tasks reported the following stack traces in /var/log/kern.log
INFO:
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team
(canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Chris J Arges
(arges)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Is this testcase reproducible using an nfs server with a recent kernel?
Lots of improvements have been made to NFS in the many years since
2.6.32, including some concurrency improvements.
Thanks,
Dave.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I also completed the same test as Chris above, without failure. I was
using Ubuntu trusty+3.13 as the server and Trusty +3.19 as the guest.
At the moment I don't see any reason to assume that there is anything
power specific in this issue, so I attempted on purely x86_64 hardware.
Also can we
I'm having an issue reproducing this problem; perhaps I'm missing
something so I'll explain my reproduction steps in detail.
Server:
1) sudo apt-get install nfs-kernel-server
2) echo '/export *(rw,sync,no_root_squash,no_subtree_check,fsid=299)' >
/etc/exports
3) sudo exportfs -a && sudo service
My apologies, I just noticed the deadlock on the mutex comment. Is this
reproducible with the upstream kernel on the client?
We provide mainline kernel builds for testing of this nature using our mainline
build repositories.
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Also keep in mind,
So I did some more searching on this including running an tcpdump in my
environment, and it appears as if idmapd is not making any requests for
me. Hence the reason we aren't hitting the deadlock. Did you do
anything specific in the area of getting idmapd up and configured?
--
You received
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
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/1509120
Title:
Process accounting
** Changed in: linux (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.net/bugs/1509120
Title:
Process accounting deadlock with idmapd callout when writing
** Package changed: ubuntu => linux (Ubuntu)
--
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/1509120
Title:
Process accounting deadlock with idmapd callout when writing to NFSv4
mount
25 matches
Mail list logo
