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

Hi!

> > > 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..

We want to do resume sometime around here, and resume wants to run
with userspace frozen, as does suspend.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/

---

• 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]>
  • Re: [PATCH] Fix failure to resume from initrds.
    • From: Linus Torvalds <[email protected]>

• Prev by Date: Do not deprecate binary semaphore or do allow mutex in software interrupt contexts
• Next by Date: Re: [RFC+PATCH] RTC calibration
• 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]