| 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, 8 Feb 2008 12:26:58 -0500 From: Vivek Goyal <vgoyal@...hat.com> To: Tomasz Chmielewski <mangoo@...g.org> Cc: Randy Dunlap <randy.dunlap@...cle.com>, LKML <linux-kernel@...r.kernel.org>, Kexec Mailing List <kexec@...ts.infradead.org>, Horms <horms@...ge.net.au> Subject: Re: why kexec insists on syncing with recent kernels? On Fri, Feb 08, 2008 at 06:19:48PM +0100, Tomasz Chmielewski wrote: > Randy Dunlap schrieb: > > (...) > >>> Even if you did -f, it must have shutdown the network. I think somehow >>> in latest kernels there is some dependency on network and that's why >>> not shutting down network in this case is helping you. >> >> I'm seeing NFS mounts take forever to unmount (at shutdown/reboot). >> (forever => 1 hour ... or never completes) >> >> Is this similar to the problem that the OP is asking about? > > Is it a diskless station? > > Even in not, just make sure you don't shut the network down before NFS is > actually unmounted...? Network is shutdown just before kexec -e finally enters the kernel and starts preparing to jump to the new kernel. Any syncing operation, or File system unmounting operation will be done before that. Can't understand why not disabling the network will help in NFS umount or syncing operation. It has to be something else. Thanks Vivek -- 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