linux-kernel - Upgrade to 2.6.24 breaks NFS service

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Feb 2008 08:58:03 +0000
From:	Nix <nix@...eri.org.uk>
To:	linux-kernel@...r.kernel.org
Subject: Upgrade to 2.6.24 breaks NFS service

I upgraded from 2.6.23.10 to 2.6.24.2 yesterday, and found NFS service
failing.

To be specific, all locks were blocking forever, with an endless flood
of

Feb 12 22:53:10 loki notice: kernel: statd: server localhost not responding, timed out
Feb 12 22:53:10 loki notice: kernel: lockd: cannot monitor esperi
Feb 12 22:53:45 loki notice: kernel: statd: server localhost not responding, timed out
Feb 12 22:53:45 loki notice: kernel: lockd: cannot monitor esperi
Feb 12 22:54:20 loki notice: kernel: statd: server localhost not responding, timed out
Feb 12 22:54:20 loki notice: kernel: lockd: cannot monitor esperi
Feb 12 22:54:55 loki notice: kernel: statd: server localhost not responding, timed out
Feb 12 22:54:55 loki notice: kernel: lockd: cannot monitor esperi
Feb 12 22:55:20 esperi notice: kernel: lockd: server loki.wkstn.nix not responding, still trying

(esperi is a UML instance on the same machine, connected via a bridged
TUN/TAP interface: the bridge, and network service to esperi and to the
rest of the local net across that bridge, was fine.)

I'm currently using NFSv3 atop nfs-utils 1.1.0.33-gdd08789, with daemons
being started in the suggested order (portmap, mountd, statd
--no-notify, nfsd). This evening I'm going to try to upgrade to
nfs-utils HEAD and see if this continues.

-- 
`The rest is a tale of post and counter-post.' --- Ian Rawlings
                                                   describes USENET
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/