On Fri, 2004-12-10 at 08:29, Stephen Smalley wrote: > force_sig_specific should definitely go into the second hook after > release of task_lock, as you will otherwise nest task_lock inside > siglock. Oops, other way around. But you understand... BTW, the description of bprm_final_setup might be a little misleading - it isn't just an issue of being possibly "slower", but rather being processing that doesn't require the task lock to still be held and that might produce undesirable lock nesting or even deadlock if the task lock is held. -- Stephen Smalley <sds@private> National Security Agency
This archive was generated by hypermail 2.1.3 : Fri Dec 10 2004 - 05:59:24 PST