Hi. On Wed, 2005-03-30 at 07:44, Pavel Machek wrote: > We currently freeze processes for suspend-to-ram, too. I guess that > disable_usermodehelper is probably better and that in_suspend() should > only be used for sanity checks... go with disable_usermodehelper and > sorry for the noise.
Here's another possibility: Freeze the workqueue that call_usermodehelper uses (remember that code I didn't push hard enough to Andrew?), and let invocations of call_usermodehelper block in TASK_UNINTERRUPTIBLE. In refrigerating processes, don't choke on kernel processes in that state. Of course if you won't want the freeze processes for str, but do want to freeze call_usermodehelper, I guess you'd still need the in_suspend() macro. Regards, Nigel -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574 Maintainer of Suspend2 Kernel Patches http://suspend2.net - 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/
