| 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
| ||
|
Date: Fri, 29 Feb 2008 02:03:05 +0100 From: Frans Pop <elendil@...net.nl> To: Trond Myklebust <trond.myklebust@....uio.no> Cc: linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [regression] nfs4: 30 second delay during umount of remote fs on system shutdown On Thursday 28 February 2008, Trond Myklebust wrote: > On Thu, 2008-02-28 at 18:29 +0100, Frans Pop wrote: > > I have verified that portmap is also not running during S31umountnfs.sh > > with 2.6.24, so apparently there has been a change in the kernel that > > has made umount look for portmap and cause the 30 second delay if it is > > not running. > > You are probably seeing the effect of lockd going down: it always > attempts to unregister from the portmapper (and no, this is _not_ new > behaviour). It is _very much_ new behavior because as soon as I boot (and shut down) with a 2.6.24 kernel the problem completely disappears. Userland is *100% identical* between my tests. > If debian is killing the portmapper while lockd is still up, then that > is a definite debian bug... I have no idea about that. AFAICT lockd is not even running (at least, there's no process named lockd, even when the system is running normally. Isn't lockd an nfs3 thing? I'm using nfs4 here. Cheers, FJP -- 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/
Powered by blists - more mailing lists