Bug 1001

Summary:	kprobes stress tests
Product:	systemtap	Reporter:	Frank Ch. Eigler <fche>
Component:	kprobes	Assignee:	Unassigned <systemtap>
Status:	RESOLVED WONTFIX
Severity:	normal
Priority:	P2
Version:	unspecified
Target Milestone:	---
Host:		Target:
Build:		Last reconfirmed:

Description Frank Ch. Eigler 2005-06-09 15:36:22 UTC

- write stress tests
- take ideas from brad.chen's testing plan
- integrate into "crashme" framework
- arrange automated runs on available RH hardware

Comment 1 Ananth Mavinakayanahalli 2008-05-12 05:14:29 UTC

Is this bug still relevant given the grind *probes have gone through in the past
3 years?

Comment 2 Frank Ch. Eigler 2008-05-12 08:29:34 UTC

> Is this bug still relevant given the grind *probes have gone through in the past
> 3 years?

While the code has certainly improved, we still don't have broad tests that
try to confirm the sufficiency of the kernel-side kprobes blacklist.  (Such
broad systemtap-level tests, corresponding to broad wildcard probes have
problems of their own.)

Comment 3 Frank Ch. Eigler 2010-04-17 15:40:50 UTC

Masami's 'perf-probe' based tool is probably the best we'll have.
Perhaps someday the kernel will pass that test.

http://lkml.org/lkml/2010/2/15/197