[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090102094730.GA17841@infradead.org>
Date: Fri, 2 Jan 2009 04:47:30 -0500
From: Christoph Hellwig <hch@...radead.org>
To: Eric Sandeen <sandeen@...deen.net>
Cc: Takashi Sato <t-sato@...jp.nec.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Hellwig <hch@...radead.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"dm-devel@...hat.com" <dm-devel@...hat.com>,
"viro@...IV.linux.org.uk" <viro@...IV.linux.org.uk>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"xfs@....sgi.com" <xfs@....sgi.com>,
"mtk.manpages@...glemail.com" <mtk.manpages@...glemail.com>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] freeze feature ver 1.14
On Thu, Jan 01, 2009 at 11:22:16PM -0600, Eric Sandeen wrote:
> In lieu of the timeout feature which was originally proposed, how
> about access to an emergency un-freeze via magic sysrq, maybe
> piggy-backed on emergency sync... something like this (not
> tested or even built yet...), would this be a good compromise to
> help save people from frozen roots?
Looks sane to me. But for that we'd need to get the generic freeze bits
in first. Andrews, as they are in 2.6.28-rc2 do you plan to send them?
Any chance for a general -mm merge plan, btw?
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists