From: Christoph Hellwig <hch@infradead.org>
To: Michael Trimarchi <trimarchimichael@yahoo.it>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Michael Trimarchi <michael@evidence.eu.com>
Subject: Re: [PATCH] Check the mtd device in do_emergency_remount()
Date: Mon, 21 Apr 2008 13:48:53 -0400 [thread overview]
Message-ID: <20080421174853.GA15690@infradead.org> (raw)
In-Reply-To: <561772.43514.qm@web26207.mail.ukl.yahoo.com>
On Mon, Apr 21, 2008 at 04:27:05PM +0000, Michael Trimarchi wrote:
> Allow superblocks managed by the mtd layer to be remounted.
Please just rip out do_emergency_remount entirely. It's the equivalent
to and attempted full-filesystem revoke and just can't work.
prev parent reply other threads:[~2008-04-21 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 16:27 [PATCH] Check the mtd device in do_emergency_remount() Michael Trimarchi
2008-04-21 17:48 ` Christoph Hellwig [this message]
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=20080421174853.GA15690@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@evidence.eu.com \
--cc=trimarchimichael@yahoo.it \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).