| 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: Wed, 09 Aug 2006 09:38:21 -0600 From: Michael Loftis <mloftis@...ps.com> To: Molle Bestefich <molle.bestefich@...il.com>, linux-kernel@...r.kernel.org Subject: Re: ext3 corruption --On August 9, 2006 5:22:28 PM +0200 Molle Bestefich <molle.bestefich@...il.com> wrote: > Messages on the console indicated that Linux actually tried to > shutdown the filesystem before shutting down Samba, which is just > plain Real-F......-Stupid. Is there no intelligent ordering of > shutdown events in Linux at all? The kernel doesn't perform those, your distro's init scripts do that. And various distros have various success at doing the right thing. I've had the best luck with Debian and Ubuntu doing this in the right order. RH seems to insist on turning off the network then network services such as sshd. > Samba was serving files to remote computers and had no desire to let > go of the filesystem while still running. After 5 seconds or so, > Linux just shutdown the MD device with the filesystem still mounted. The kernel probably didn't do this, usually by the time the kernel gets to this point init has already sent kills to everything. If it hasn't it points to problems with your init scripts, not the kernel. > > That's what happened on a user-visible level, but what could have > happened internally in the filesystem? - 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