* Oleg Nesterov <oleg@xxxxxxxxxx> [2011-10-07 18:58:28]: > > Agreed, this looks much, much better. In both cases the task is current, > it is safe to change ->blocked. > > But please avoid sigprocmask(), we have set_current_blocked(). Sure, I will use set_current_blocked(). While we are here, do you suggest I re-use current->saved_sigmask and hence use set_restore_sigmask() while resetting the sigmask? I see saved_sigmask being used just before task sleeps and restored when task is scheduled back. So I dont see a case where using saved_sigmask in uprobes could conflict with its current usage. However if you prefer we use a different sigmask to save and restore, I can make it part of the utask structure. -- Thanks and Regards Srikar -- 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>