From: Christoph Hellwig <hch@infradead.org>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
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: Mon, 5 Feb 2007 21:35:30 +0000 [thread overview]
Message-ID: <20070205213530.GA9794@infradead.org> (raw)
In-Reply-To: <1170710913.6105.39.camel@nigel.suspend2.net>
On Tue, Feb 06, 2007 at 08:28:33AM +1100, Nigel Cunningham wrote:
> Why do you think remounting filesystems is necessary? Are you getting
> problems with some particular filesystem?
>
> If I recall correctly, we briefly tried remounting filesystems in
> Suspend2, but it created problems with logging - some files open r/w
> were readonly afterwards.
Yes, that's the biggest problem with the forced remount r/o hack -
FMODE_WRITE is dropped from all files, and can't be recovered.
(and at the same time in progress writes or writes through shared
mmaps are totally ignored).
> We then tried bdev freezing with much better success.
Yes, that's the right thing to do if you want to be safe, but
we already had that discussion..
next prev parent reply other threads:[~2007-02-05 21:36 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 [this message]
2007-02-06 14:32 ` Henrique de Moraes Holschuh
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=20070205213530.GA9794@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=akuster@mvista.com \
--cc=hmh@hmh.eng.br \
--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).