On Wed, Nov 09, 2011 at 08:59:25AM -0800, Tejun Heo wrote: > Freezer depends on the usual "set_current_state(INTERRUPTIBLE); check > freezing; schedule(); check freezing" construct and sends > INTERRUPTIBLE wake up after setting freezing state. The > synchronization hasn't been completely clear but recently been cleaned > up, so as long as freezing condition is tested after INTERRUPTIBLE is > set before going to sleep, the event won't go missing. Just in case, it's scheduled for the next merge window but TIF_FREEZE is gone now. There is freezing() helper which tests all pending freezing conditions and the freezer guarantees there's mb between assertion of freezing() and sending interruptible wakeups to target tasks. Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>