From: Pavel Machek <pavel@ucw.cz>
To: Rob Landley <rob@landley.net>
Cc: M?ns Rullg?rd <mru@users.sourceforge.net>,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: [Swsusp-devel] Re: [PATCH] Allow initrd_load() before software_resume() (version 2)
Date: Mon, 11 Aug 2003 17:29:31 +0200 [thread overview]
Message-ID: <20030811152931.GA2627@elf.ucw.cz> (raw)
In-Reply-To: <200308102208.10588.rob@landley.net>
Hi!
> > >> > > Okay. I hadn't tried it yet. I'll happily take up the barrow for you
> > >> > > and push it to Pavel and Linus with the rest, if you like.
> > >> >
> > >> > Don't even think about that.
> > >> >
> > >> > It is not safe to run userspace *before* doing resume. You don't want
> > >> > to see problems this would bring in. Forget it.
> > >>
> > >> so how do you resume from a partition on a device mapper volume?
> > >>
> > >> (and yes I basically agree with your sentiment though)
> > >
> > > I know very little about DM, its very well possible that resume from
> > > it is not supported.
> >
> > Since DM requires some userspace program to set up the mappings, it
> > seems to me that it wouldn't work to resume from a DM volume. I'd
> > much appreciate if it would work, somehow.
>
> Er, query:
>
> At some point in the vague nebulous future, after initrd has become initramfs,
> the partition detection code is scheduled to be ripped out, correct? And
> replaced with a userspace thing run out of initrd ala hotplug and udev and
> all that?
>
> So at that point, it's not just device mapper that's going to need something
> else to run in userspace to attach block devices to partitions. Everything
> will.
>
> So are you saying that swsusp is a short-term thing that will be dropped in
> 2.8 because it can't be made to work? Or that we WILL have to deal with this
> at some point, just not yet?
At that point we'll have to carefully audit all userland code that can
run before software resume.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2003-08-11 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 0:29 [PATCH] Allow initrd_load() before software_resume() Pascal Brisset
2003-08-01 1:18 ` Nigel Cunningham
2003-08-01 10:32 ` [PATCH] Allow initrd_load() before software_resume() (version 2) Pascal Brisset
2003-08-01 10:41 ` [Swsusp-devel] " Nigel Cunningham
2003-08-06 11:30 ` Pavel Machek
2003-08-06 11:47 ` Arjan van de Ven
2003-08-06 12:57 ` Pavel Machek
2003-08-06 13:16 ` Måns Rullgård
2003-08-11 2:08 ` Rob Landley
2003-08-11 15:29 ` Pavel Machek [this message]
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=20030811152931.GA2627@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@users.sourceforge.net \
--cc=rob@landley.net \
/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).