The patch titled
kprobes: NULL out non-relevant fields in struct kretprobe
has been removed from the -mm tree. Its filename is
kprobes-null-out-non-relevant-fields-in-struct-kretprobe.patch
This patch was probably dropped from -mm because
it has now been merged into a subsystem tree or
into Linus's tree, or because it was folded into
its parent patch in the -mm tree.
From: Ananth N Mavinakayanahalli <ananth@xxxxxxxxxx>
In cases where a struct kretprobe's *_handler fields are non-NULL, it is
possible to cause a system crash, due to the possibility of calls ending up
in zombie functions. Documentation clearly states that unused *_handlers
should be set to NULL, but kprobe users sometimes fail to do so.
Fix it by setting the non-relevant fields of the struct kretprobe to NULL.
Signed-off-by: Ananth N Mavinakayanahalli <ananth@xxxxxxxxxx>
Acked-by: Jim Keniston <jkenisto@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
kernel/kprobes.c | 3 +++
1 files changed, 3 insertions(+)
diff -puN kernel/kprobes.c~kprobes-null-out-non-relevant-fields-in-struct-kretprobe kernel/kprobes.c
--- devel/kernel/kprobes.c~kprobes-null-out-non-relevant-fields-in-struct-kretprobe 2006-04-20 02:37:03.000000000 -0700
+++ devel-akpm/kernel/kprobes.c 2006-04-20 02:37:03.000000000 -0700
@@ -585,6 +585,9 @@ int __kprobes register_kretprobe(struct
int i;
rp->kp.pre_handler = pre_handler_kretprobe;
+ rp->kp.post_handler = NULL;
+ rp->kp.fault_handler = NULL;
+ rp->kp.break_handler = NULL;
/* Pre-allocate memory for max kretprobe instances */
if (rp->maxactive <= 0) {
_
Patches currently in -mm which might be from ananth@xxxxxxxxxx are
origin.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
