Re: [PATCH] Fix failure to resume from initrds.

On Tue, 11 Sep 2007, Rafael J. Wysocki wrote:
> > 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.

Umm. All of this is __init code - why is freezability even an issue? We 
shouldn't be suspending at this point anyway afaik..

Is suspend2 perhaps doing something different here? 

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] Fix failure to resume from initrds.
    • From: Pavel Machek <[email protected]>

• References:
  • [PATCH] Fix failure to resume from initrds.
    • From: Nigel Cunningham <[email protected]>
  • Re: [PATCH] Fix failure to resume from initrds.
    • From: "Rafael J. Wysocki" <[email protected]>
  • Re: [PATCH] Fix failure to resume from initrds.
    • From: "Rafael J. Wysocki" <[email protected]>
  • Re: [PATCH] Fix failure to resume from initrds.
    • From: "Rafael J. Wysocki" <[email protected]>

• Prev by Date: Re: [00/41] Large Blocksize Support V7 (adds memmap support)
• Next by Date: [PATCH] Configurable tap interface MTU
• Previous by thread: Re: [PATCH] Fix failure to resume from initrds.
• Next by thread: Re: [PATCH] Fix failure to resume from initrds.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]