public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: nigel@suspend2.net, LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Pavel Machek <pavel@ucw.cz>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Fix failure to resume from initrds.
Date: Tue, 11 Sep 2007 23:41:20 +1000	[thread overview]
Message-ID: <200709112341.21225.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <200709111523.33968.rjw@sisk.pl>

Hi.

On Tuesday 11 September 2007 23:23:32 Rafael J. Wysocki wrote:
> On Tuesday, 11 September 2007 15:12, Rafael J. Wysocki wrote:
> > On Tuesday, 11 September 2007 13:55, Rafael J. Wysocki wrote:
> > > On Tuesday, 11 September 2007 13:27, Nigel Cunningham wrote:
> > > > Hi.
> > > > 
> > > > On Tuesday 11 September 2007 21:04:22 Rafael J. Wysocki wrote:
> > > > > On Tuesday, 11 September 2007 05:54, Nigel Cunningham wrote:
> > > > > > Hi all.
> > > > > > 
> > > > > > Commit 831441862956fffa17b9801db37e6ea1650b0f69 (Freezer: make 
kernel 
> > > > threads
> > > > > > nonfreezable by default) breaks freezing when attempting to resume 
from an
> > > > > > initrd, because the init (which is freezeable) spins while waiting 
for 
> > > > another
> > > > > > thread to run /linuxrc, but doesn't check whether it has been told 
to 
> > > > enter
> > > > > > the refrigerator.
> > > > > 
> > > > > Hm.
> > > > > 
> > > > > I use a resume from an initrd on a regular basis and it works 
without the 
> > > > patch
> > > > > below.
> > > > > 
> > > > > I think we need to investigate what happens in your test case a bit.
> > > > 
> > > > Ah. That makes me realise that I see that too - my AMD64 uniprocessor 
laptop 
> > > > didn't need the patch (guess that's why I didn't notice the need and 
ack'd 
> > > > the patch). But my x86 SMP machine... it needs this. I'll see if 
they're 
> > > > running on different processors.
> > > 
> > > Well, strange.  My x86_64 SMP machines don't need the patch too.
> > 
> > Anyway, yes, init is freezable, but should it be?
> > 
> > I mean, shouldn't we rather add PF_NOFREEZE to kernel_init()?
> 
> Argh, no.  PF_NOFREEZE is inherited by the children.
> 
> So, I think that your patch is correct, but there's some suspend2-specific
> stuff in it.  I've rediffed it against 2.6.23-rc6 and moved try_to_freeze()
> before yield().

Ah yeah. Sorry about that. Is there some reason I've forgotten that makes the 
order of try_to_freeze & yield in a loop like this matter?

By the way, I had a go at getting fuse processes frozen today. Seems to be 
doable if you take a freeze filesystems prior to processes approach. I've got 
a lot more testing and a bit of cleaning up to do before I'd want to show it 
to anyone, but did successfully do cycles with sshfs, fuseiso and curlftpfs. 
Of course I don't seriously expect it to get merged - everyone's too much in 
love with kexec at the moment :)

Regards,

Nigel
-- 
See http://www.tuxonice.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.

  reply	other threads:[~2007-09-11 13:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11  3:54 [PATCH] Fix failure to resume from initrds Nigel Cunningham
2007-09-11 11:04 ` Rafael J. Wysocki
2007-09-11 11:27   ` Nigel Cunningham
2007-09-11 11:55     ` Rafael J. Wysocki
2007-09-11 13:01       ` Nigel Cunningham
2007-09-11 13:12       ` Rafael J. Wysocki
2007-09-11 13:23         ` Rafael J. Wysocki
2007-09-11 13:41           ` Nigel Cunningham [this message]
2007-09-11 19:25             ` Rafael J. Wysocki
2007-09-11 14:39           ` Linus Torvalds
2007-09-11 16:27             ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2007-09-14 12:22 Rafael J. Wysocki
2007-09-14 12:20 ` 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=200709112341.21225.nigel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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