Re: [PATCH] Remove process freezer from suspend to RAM pathway

Am Dienstag, 3. Juli 2007 schrieb Rafael J. Wysocki:
> > > The main reason for deadlocks is because we do a sys_sync() after the
> > > freeze, which we shouldn't do.
> > 
> > So why don't we remove the sys_sync() from freeze_processes() instead?
> 
> The patch follows (untested).

And a further question. The freezer is not atomic. What do you do
if a task not yet frozen calls sys_sync(), but fuse is already frozen?

	Regards
		Oliver
-
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] Remove process freezer from suspend to RAM pathway
    • From: "Rafael J. Wysocki" <[email protected]>
  • Re: [PATCH] Remove process freezer from suspend to RAM pathway
    • From: Miklos Szeredi <[email protected]>

• References:
  • [PATCH] Remove process freezer from suspend to RAM pathway
    • From: Matthew Garrett <[email protected]>
  • Re: [PATCH] Remove process freezer from suspend to RAM pathway
    • From: "Rafael J. Wysocki" <[email protected]>
  • Re: [PATCH] Remove process freezer from suspend to RAM pathway
    • From: "Rafael J. Wysocki" <[email protected]>

• Prev by Date: Re: [patch 10/10] Scheduler profiling - Use immediate values
• Next by Date: Re: Concerning a post that you made about expandable anonymous shared mappings
• Previous by thread: Re: [PATCH] Remove process freezer from suspend to RAM pathway
• Next by thread: Re: [PATCH] Remove process freezer from suspend to RAM pathway
• 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]