From: Pavel Machek <pavel@ucw.cz>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SOFTWARE_SUSPEND as a module
Date: Fri, 23 Apr 2004 14:56:50 +0200 [thread overview]
Message-ID: <20040423125650.GA30503@elf.ucw.cz> (raw)
In-Reply-To: <20040423122738.GA12504@gondor.apana.org.au>
Hi!
> > If you really ensure userspace is stopped, you should be fine.
> >
> > *But* kernel is only correct if userspace is "correct", and need for
> > all processes stopped is not going to be obvious to users. I'd like
> > kernel to be kernel to be okay regardless what stupid stuff happens in
> > userspace. (Well, they really should not scribble on disks).
>
> But in this context if user space is not doing the right thing,
> you'll lose whatever the kernel does. For example, if user space
> writes to any file systems mounted in the suspended image, then
> you'll get corruption no matter what the kernel does.
Hmm, this should keep users from doing so. Alternative solution is to
add your own warning ;-).
Pavel
* BIG FAT WARNING *********************************************************
*
* If you touch anything on disk between suspend and resume...
* ...kiss your data goodbye.
*
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-04-23 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 12:04 SOFTWARE_SUSPEND as a module Herbert Xu
2004-04-23 0:56 ` Pavel Machek
2004-04-23 9:38 ` Herbert Xu
2004-04-23 12:21 ` Pavel Machek
2004-04-23 12:27 ` Herbert Xu
2004-04-23 12:56 ` Pavel Machek [this message]
2004-04-23 13:28 ` Nigel Cunningham
2004-04-23 14:30 ` Martin Hermanowski
2004-04-26 12:28 ` 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=20040423125650.GA30503@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=herbert@gondor.apana.org.au \
--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