[PATCH 0/2] never check task->signal != NULL

From: Oleg Nesterov
Date: Thu Mar 18 2010 - 14:55:18 EST

Next message: Oleg Nesterov: "[PATCH 2/2] ia64: ptrace_attach_sync_user_rbs: avoid "task->signal!= NULL" checks"
Previous message: Andrew Morton: "Re: [PATCH] dm: max_segments=1 if merge_bvec_fn is not supported"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Another preparation to make task->signal immutable, this is the only
necessary change outside of fork/exit pathes.

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Oleg Nesterov: "[PATCH 2/2] ia64: ptrace_attach_sync_user_rbs: avoid "task->signal!= NULL" checks"
Previous message: Andrew Morton: "Re: [PATCH] dm: max_segments=1 if merge_bvec_fn is not supported"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]