This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug documentation/11224] setting module arguments needs to be tested/documented
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 3 Feb 2010 21:36:29 -0000
- Subject: [Bug documentation/11224] setting module arguments needs to be tested/documented
- References: <20100126221502.11224.dsmith@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From jistone at redhat dot com 2010-02-03 21:36 -------
(In reply to comment #6)
> [...] it seems like if we are going to make this feature optional it would
> be safer as opt-in rather than opt-out.
I agree, and I would prefer for this to be more explicit than just whether it
was initialized or not. One possibility is a new keyword to augment or replace
the global keyword for parameterized variables. (e.g. extern/param/...)
> Also, it would be nice from a user/scripting perspective if staprun one.ko
> nonexistant_variable=a would run with a warning instead of terminating with an
> error :)
I disagree, because then you get the class of bug reports like "Why doesn't
setting this parameter change anything? Oh, because I used the wrong name..."
I think this is not under our control anyway, because we're using the kernel's
module-parameter facility. We could perhaps improve the error message though.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11224
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.