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

On Tue, Jul 03, 2007 at 08:13:53AM +0200, Oliver Neukum wrote:

> Only if you want to audit all character devices' read() and write()
> methods for races against suspend().
> / on fuse is a bad idea.

Any driver that assumes that userspace will be frozen during suspend has 
been broken forever. That behaviour has never been guaranteed.
-- 
Matthew Garrett | [email protected]
-
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]>

• 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: Oliver Neukum <[email protected]>

• Prev by Date: [patch 5/5] s390 tlb flush fix.
• Next by Date: Re: [PATCH 1/1] file caps: update selinux xattr hooks
• 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]