Prev: bfa: wrong fcport H2I message tested in bfa_fcport_isr()
Next: [PATCH 16/18] Generate empty tracepoints if syscall tracing is disabled
From: Paul Menage on 22 Mar 2010 20:00
On Mon, Mar 22, 2010 at 3:22 AM, Oleg Nesterov <oleg(a)redhat.com> wrote:
>
> Please use ->signal instead. By the lucky coincidence the lifetime rules
> for (greatly misnamed) signal_struct were changed recently in -mm.
>
> With the recent changes, it is always safe to use task->signal. It can't
> be changed, can't go away, no need to bump the counter, no races, etc.
>
> What do you think?

If signal_struct is much simpler to reason about, then using it seems
like a good idea.

Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: bfa: wrong fcport H2I message tested in bfa_fcport_isr()
Next: [PATCH 16/18] Generate empty tracepoints if syscall tracing is disabled