From: Valdis.Kletnieks@vt.edu
To: Pavel Machek <pavel@suse.cz>
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 10:17:09 -0500 [thread overview]
Message-ID: <16406.1232119029@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 16 Jan 2009 09:48:28 +0100." <20090116084828.GB4795@atrey.karlin.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
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?
Hmm.. guess you *could* get into trouble if you tried to do a Sysrq-[not-s]
and hit the wrong key - but you have the same danger if you have *any*
sysrq- invoking an emergency_thaw and hit it by accident...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-01-16 15:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 4:06 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 [this message]
2009-01-16 15:28 ` Eric Sandeen
2009-01-16 15:33 ` Pavel Machek
2009-01-16 15:40 ` Theodore Tso
2009-01-16 15:52 ` Valdis.Kletnieks
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 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=16406.1232119029@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®