public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Maitin-Shepard <jbms@cmu.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Miklos Szeredi <miklos@szeredi.hu>,
	LKML <linux-kernel@vger.kernel.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC][PATCH -mm] Freezer: Handle uninterruptible tasks
Date: Mon, 09 Jul 2007 00:21:32 -0400	[thread overview]
Message-ID: <87odimw6k3.fsf@jbms.ath.cx> (raw)
In-Reply-To: <20070708120933.GA3866@ucw.cz> (Pavel Machek's message of "Sun\, 8 Jul 2007 12\:09\:33 +0000")

Pavel Machek <pavel@ucw.cz> writes:

[snip]

> I don't know how to do that mechanism... but if we knew where to trap
> filesystem writes, we could simply freeze at that point, and at that
> point only, no?

Any operation at all that has an external effect must not occur after
the snapshot is made; otherwise, there will be random hard-to-find
corruptions and other problems occurring as a result.  Thus, for
example, any writes (either directly or indirectly through e.g. a
filesystem) to non-volatile storage, any network traffic, any
communication with hardware like a printer must be prevented after the
snapshot.  It seems, though, that in general the kernel will have no way
to know which operations are safe, and which are not safe.

(This is why the whole "proper filesystem snapshot support is the
solution" argument is bogus.)

-- 
Jeremy Maitin-Shepard

  parent reply	other threads:[~2007-07-09  4:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.0707061039380.3737-100000@iolanthe.rowland.org>
2007-07-07 23:08 ` [RFC][PATCH -mm] Freezer: Handle uninterruptible tasks Rafael J. Wysocki
     [not found] ` <200707080108.17371.rjw@sisk.pl>
2007-07-08 12:09   ` Pavel Machek
     [not found]   ` <20070708120933.GA3866@ucw.cz>
2007-07-08 13:55     ` Rafael J. Wysocki
2007-07-09  4:21     ` Jeremy Maitin-Shepard [this message]
2007-07-09 14:45       ` Alan Stern
2007-07-08 18:37   ` Pavel Machek
     [not found] <Pine.LNX.4.44L0.0707091043480.3851-100000@iolanthe.rowland.org>
2007-07-09 15:36 ` Jeremy Maitin-Shepard
     [not found] <200707061012.48998.rjw@sisk.pl>
2007-07-06 15:01 ` Alan Stern
2007-07-07  7:50 ` Pavel Machek
2007-07-07  9:13   ` Nigel Cunningham
     [not found]   ` <200707071913.43482.nigel@nigel.suspend2.net>
2007-07-07 11:31     ` Pavel Machek
2007-07-07 20:44       ` Rafael J. Wysocki
2007-07-06  8:12 Rafael J. Wysocki

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=87odimw6k3.fsf@jbms.ath.cx \
    --to=jbms@cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=miklos@szeredi.hu \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@ucw.cz \
    /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