| 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
| ||
|
Message-Id: <200802281829.16343.elendil@planet.nl> Date: Thu, 28 Feb 2008 18:29:15 +0100 From: Frans Pop <elendil@...net.nl> To: linux-nfs@...r.kernel.org Cc: linux-kernel@...r.kernel.org Subject: [regression] nfs4: 30 second delay during umount of remote fs on system shutdown With 2.6.25-rc2 and -rc3 I noticed a pause of 30 seconds when my system (Debian unstable, x86_64) is being shutdown. The cause is the unmounting of an nfs4 remote file system. The pause does not happen with 2.6.24. I'm unsure about 2.6.25-rc1 as I was concentrating on other issues when I was testing that. I can reproduce the same pause on an active system by stopping portmap before doing an umount of the filesystem. The shutdown sequence on my box includes: K20nfs-common [...] S20sendsigs [...] S31umountnfs.sh S32portmap So it seems that things should be OK (S32portmap is after S31umountnfs.sh), but in fact portmap has already been killed during S20sendsigs! 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. Is this a kernel regression? 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