From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
t-sato@yk.jp.nec.com
Subject: Re: [PATCH] Allow SysRq emergency sync to thaw frozen filesystems
Date: Thu, 15 Jan 2009 16:20:31 -0800 [thread overview]
Message-ID: <20090115162031.a512232b.akpm@linux-foundation.org> (raw)
In-Reply-To: <496EB639.6090800@redhat.com>
On Wed, 14 Jan 2009 22:06:17 -0600
Eric Sandeen <sandeen@redhat.com> wrote:
> Now that the filesystem freeze operation has been elevated
> to the VFS, and is just an ioctl away, some sort of safety net
> for unintentionally frozen root filesystems may be in order.
>
> The timeout thaw originally proposed did not get merged, but
> perhaps something like this would be useful in emergencies.
>
> This doesn't have to piggyback on the existing emergency sync
> sysrq, but it seems like a reasonable, simple addition to me.
>
> I've tested this on a non-root fs with multiple (nested) freezers,
> as well as on a system rendered unresponsive due to a frozen
> root fs.
Worried.
Under what operational scenarios is ths feature actually needed/used?
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> Index: linux-2.6/drivers/char/sysrq.c
> ===================================================================
> --- linux-2.6.orig/drivers/char/sysrq.c
> +++ linux-2.6/drivers/char/sysrq.c
> @@ -151,6 +151,7 @@ static struct sysrq_key_op sysrq_reboot_
>
> static void sysrq_handle_sync(int key, struct tty_struct *tty)
> {
> + emergency_thaw();
> emergency_sync();
> }
Kind of weird. The thaw will happen after/during the sync().
I guess that if the sync is blocked on a frozen fs then things will
sort themselves out.
otoh, if all the pdflush threads are blocked on frozen filesystems
(possible?) then the emergency_thaw() simply won't do anything.
> ===================================================================
> --- linux-2.6.orig/fs/buffer.c
> +++ linux-2.6/fs/buffer.c
> @@ -258,6 +258,29 @@ struct super_block *freeze_bdev(struct b
> }
> EXPORT_SYMBOL(freeze_bdev);
>
> +void do_thaw(unsigned long unused)
> +{
> + struct super_block *sb;
> + char b[BDEVNAME_SIZE];
> +
> + list_for_each_entry(sb, &super_blocks, s_list) {
> + while (sb->s_bdev && !thaw_bdev(sb->s_bdev, sb))
> + printk(KERN_WARNING "Emergency Thaw on %s\n",
> + bdevname(sb->s_bdev, b));
hm, I made the args to bdevname() backwards. Bad me.
> + }
> + printk(KERN_WARNING "Emergency Thaw complete\n");
> +}
next prev parent reply other threads:[~2009-01-16 0:21 UTC|newest]
Thread overview: 30+ 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 [this message]
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
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=20090115162031.a512232b.akpm@linux-foundation.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox