| 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: <20090116153345.GC2022@elf.ucw.cz> Date: Fri, 16 Jan 2009 16:33:46 +0100 From: Pavel Machek <pavel@...e.cz> To: Valdis.Kletnieks@...edu Cc: Eric Sandeen <sandeen@...hat.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-kernel Mailing List <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Takashi Sato <t-sato@...jp.nec.com> Subject: Re: [PATCH] Allow SysRq emergency sync to thaw frozen filesystems On Fri 2009-01-16 10:17:09, Valdis.Kletnieks@...edu wrote: > On Fri, 16 Jan 2009 09:48:28 +0100, Pavel Machek said: > > > Emergency Sync should not do this. Invent another key. > > > > ...because otherwise, if you hit emergency sync but the system is > > still alive and relies on filesystem freezing, bad stuff will happen. > > Under what conditions would a system be alive and relying on freezing, > *and* an emergency thaw would be worse than whatever reason you're doing > an emergency sync? I sometimes hit emergency sync on perfectly healthy system... like before "insmod shiny-new-guaranteed-to-work-module"... I believe sysrq-s should not have sideffects. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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