From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
akuster@mvista.com, linux-kernel@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [patch 1/1] PM: Adds remount fs ro at suspend
Date: Tue, 6 Feb 2007 12:32:31 -0200 [thread overview]
Message-ID: <20070206143231.GD18392@khazad-dum.debian.net> (raw)
In-Reply-To: <1170710913.6105.39.camel@nigel.suspend2.net>
On Tue, 06 Feb 2007, Nigel Cunningham wrote:
> Why do you think remounting filesystems is necessary? Are you getting
> problems with some particular filesystem?
No. But anything in a removable device neets to be either remounted
read-only or unmounted if that is at all possible, because the user could
unplug it. It is of course, sync'd anyway, so if the remount/umount fails,
no corruption should happen... but the fs will be dirty, etc.
It can get very ugly when you factor in docks and removable bays. It's not
just USB/firewire mass-storage devices and memory cards. And there is the
patological cases where the user suspends with the device in one port, and
resumes with the device in another port.
I feel userspace *can* do all that needs to be done, but we are (currently)
very bad at it.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-02-06 14:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 23:50 [patch 1/1] PM: Adds remount fs ro at suspend akuster
2007-02-03 0:16 ` Andrew Morton
2007-02-03 0:35 ` Henrique de Moraes Holschuh
2007-02-05 21:28 ` Nigel Cunningham
2007-02-05 21:35 ` Christoph Hellwig
2007-02-06 14:32 ` Henrique de Moraes Holschuh [this message]
2007-02-06 18:07 ` Rafael J. Wysocki
2007-02-06 21:38 ` Nigel Cunningham
2007-02-07 11:25 ` Henrique de Moraes Holschuh
2007-02-07 11:43 ` Nigel Cunningham
2007-02-07 12:05 ` Henrique de Moraes Holschuh
2007-02-07 14:10 ` Rafael J. Wysocki
2007-02-09 22:24 ` Pavel Machek
2007-02-13 12:12 ` Pavel Machek
2007-02-03 0:57 ` akuster
2007-02-03 10:08 ` Christoph Hellwig
2007-02-04 1:34 ` akuster
2007-02-05 16:56 ` Christoph Hellwig
2007-02-14 11:07 ` Pavel Machek
2007-02-03 16:19 ` Pavel Machek
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=20070206143231.GD18392@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=akpm@linux-foundation.org \
--cc=akuster@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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).