From: ebiederm@xmission.com (Eric W. Biederman)
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, haveblue@us.ibm.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH[RFC] kill sysrq-u (emergency remount r/o)
Date: Mon, 05 Feb 2007 17:15:14 -0700 [thread overview]
Message-ID: <m17iuww38t.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070205173247.GA25790@lst.de> (Christoph Hellwig's message of "Mon, 5 Feb 2007 18:32:47 +0100")
Christoph Hellwig <hch@lst.de> writes:
> Hi there,
>
> in two recent discussions (file_list_lock scalability and remount r/o
> on suspend) I stumbled over this emergency remount feature. It's not
> actually useful because it tries a potentially dangerous remount
> despite writers still beeing in progress, which we can't get rid.
>
> I've attached one patch in this mail that simply kills the
> functionality, and in a reply to this mail I'll send a second one
> that keeps the sysrq functionality, but removes the force argument
> from do_remount_sb that overrides the still busy check. This version
> is currently not useful, but makes a lot of sense once Dave Hansens
> per-mountpoint r/o patches get in, as we can check for a real write
> in progress instead of simply a file opened with write permission.
>
> Any ideas and comments?
Most things that sysrq allows you to do are dubious but work most
of the time, and are much better than the alternatives. Synching and
remounting read-only are several of those, so is rebooting. If you
look at the emergency reboot path it doesn't do the clean shutdown
that every other reboot path does.
So if it is a maintenance problem I'm inclined to believe there is
a problem that needs fixing. Otherwise I'm not certain you understand
the point of making thees things available with sysrq.
Eric
next prev parent reply other threads:[~2007-02-06 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 17:32 Christoph Hellwig
2007-02-05 17:34 ` [PATCH[RFC] don't force remount in " Christoph Hellwig
2007-02-05 20:40 ` [PATCH[RFC] kill " Jan Engelhardt
2007-02-06 3:17 ` Theodore Tso
2007-02-06 9:44 ` Christoph Hellwig
2007-02-06 0:15 ` Eric W. Biederman [this message]
2007-02-06 0:45 ` Nigel Cunningham
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=m17iuww38t.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome