From: Pavel Machek <pavel@suse.cz>
To: Valdis.Kletnieks@vt.edu
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Takashi Sato <t-sato@yk.jp.nec.com>
Subject: Re: [PATCH] Allow SysRq emergency sync to thaw frozen filesystems
Date: Fri, 16 Jan 2009 16:33:46 +0100 [thread overview]
Message-ID: <20090116153345.GC2022@elf.ucw.cz> (raw)
In-Reply-To: <16406.1232119029@turing-police.cc.vt.edu>
On Fri 2009-01-16 10:17:09, Valdis.Kletnieks@vt.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
next prev parent reply other threads:[~2009-01-16 15:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 4:06 [PATCH] Allow SysRq emergency sync to thaw frozen filesystems Eric Sandeen
2009-01-16 0:20 ` Andrew Morton
2009-01-16 3:49 ` Eric Sandeen
2009-01-16 3:59 ` Eric Sandeen
2009-01-16 15:33 ` Valdis.Kletnieks
2009-01-16 15:40 ` Eric Sandeen
2009-01-16 16:21 ` Dave Kleikamp
2009-01-16 16:42 ` Dave Kleikamp
2009-01-16 8:48 ` Pavel Machek
2009-01-16 15:17 ` Valdis.Kletnieks
2009-01-16 15:28 ` Eric Sandeen
2009-01-16 15:33 ` Pavel Machek [this message]
2009-01-16 15:40 ` Theodore Tso
2009-01-16 15:52 ` Valdis.Kletnieks
2009-01-16 16:08 ` Eric Sandeen
2009-01-16 16:08 ` Eric Sandeen
2009-01-16 19:31 ` [PATCH V2] Allow SysRq emergency thaw " Eric Sandeen
2009-01-16 19:38 ` Randy Dunlap
2009-01-16 19:46 ` Eric Sandeen
2009-01-16 19:50 ` [PATCH V3] " Eric Sandeen
2009-01-30 21:40 ` Andrew Morton
2009-02-02 22:55 ` [PATCH V4] " Eric Sandeen
2009-02-03 11:48 ` Jamie Lokier
2009-02-03 13:31 ` Dave Kleikamp
2009-02-03 21:21 ` Dave Chinner
2009-02-03 22:01 ` Andrew Morton
2009-02-03 22:07 ` Eric Sandeen
2009-02-03 22:21 ` Andrew Morton
2009-02-16 22:01 ` [PATCH V5] " Eric Sandeen
[not found] <bUrIs-Za-3@gated-at.bofh.it>
[not found] ` <bUKL7-6vo-3@gated-at.bofh.it>
[not found] ` <bUNSJ-2Vn-13@gated-at.bofh.it>
[not found] ` <bUO2t-376-5@gated-at.bofh.it>
[not found] ` <bUYXL-3Qb-25@gated-at.bofh.it>
[not found] ` <bUZ7p-448-9@gated-at.bofh.it>
2009-01-17 14:03 ` [PATCH] Allow SysRq emergency sync " Bodo Eggert
2009-01-17 14:03 ` Bodo Eggert
2009-01-17 15:44 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090116153345.GC2022@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=t-sato@yk.jp.nec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.