fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
sin8h has joined #systemtap
sjas has quit [Quit: WeeChat 1.4]
sin8h has quit [Quit: Leaving.]
sin8h has joined #systemtap
sin8h has quit [Client Quit]
naveen has joined #systemtap
naveen has quit [Quit: Leaving.]
sin8h has joined #systemtap
sin8h has quit [Quit: Leaving.]
sin8h has joined #systemtap
drsmith has joined #systemtap
drsmith has left #systemtap [#systemtap]
hkshaw has joined #systemtap
ananth has joined #systemtap
hkshaw has quit [Ping timeout: 240 seconds]
ego has joined #systemtap
srikar_away is now known as srikar
hkshaw has joined #systemtap
hkshaw has quit [Read error: Connection reset by peer]
hkshaw has joined #systemtap
dancancode has quit [Ping timeout: 256 seconds]
dancancode has joined #systemtap
srikar is now known as srikar_away
srikar_away is now known as srikar
ego has quit [Ping timeout: 250 seconds]
dancancode has left #systemtap ["Be back later ..."]
sin8h has quit [Quit: Leaving.]
ego has joined #systemtap
hkshaw has quit [Quit: Leaving.]
hkshaw has joined #systemtap
srikar is now known as srikar_away
srikar_away is now known as srikar
jistone has quit [Ping timeout: 240 seconds]
jistone has joined #systemtap
sin8h has joined #systemtap
modem_ has joined #systemtap
hkshaw1 has joined #systemtap
hkshaw has quit [Ping timeout: 245 seconds]
hkshaw1 has quit [Ping timeout: 245 seconds]
hkshaw has joined #systemtap
ego has quit [Ping timeout: 256 seconds]
hkshaw has quit [Ping timeout: 252 seconds]
sin8h has quit [Quit: Leaving.]
sin8h has joined #systemtap
sin8h has quit [Quit: Leaving.]
ananth has quit [Quit: Leaving]
sin8h has joined #systemtap
mjw has joined #systemtap
flu_ has joined #systemtap
sin8h has quit [Quit: Leaving.]
sin8h has joined #systemtap
drsmith has joined #systemtap
mbenitez has joined #systemtap
mbenitez has joined #systemtap
tromey has joined #systemtap
<lorddoskias>
is it possible to silence systemtap when it finds module version mismatches (due to multiple compilations)?
<fche>
lorddoskias, like the buildid mismatch warnings?
<lorddoskias>
more like: ERROR: module version mismatch (#49 SMP Wed Feb 10 15:37:04 EET 2016 vs #48 SMP Wed Feb 10 12:02:37 EET 2016), release 3.12.51-clouder3
<lorddoskias>
so yeah, the build number is incremented
<fche>
we try to be very careful about assuming binary compatibility between kernel headers and running binaries
<fche>
if we're running on a different version of the kernel, we have no guarantee that the same kernel configuration is used e.g.
<lorddoskias>
yeah, but is there a way to override this?
<lorddoskias>
a la guru mode?
<lorddoskias>
(tried it to no avail)
<fche>
hm, perhaps we could relax that check with -g mode, or perhaps a -D flag (maybe there is one already)
<lorddoskias>
because what i did now is modify the source of the module and recompile, which naturally bumped up the build number but fundamentally nothing changed on the core kernel side
brolley has joined #systemtap
<fche>
there is a series of checks that stap emits, not just that one, and there's currently no knob to override them
<fche>
see translate.cxx c_unparser::emit_module_init
<lorddoskias>
i as jsut reading this file
<fche>
there is a -DSTP_NO_BUILDID_CHECK that disables build-id hash checking
<fche>
we could consider another -DSTP_NO_VERREL_CHECK or something to disable the other stuff in translate.cxx
<lorddoskias>
so i'm reading this line: o->newline(1) << "_stp_error (\"module release mismatch (%s vs %s)\", "
<fche>
suppress the ->version check just afterwards
<fche>
and some other stuff just before IIRC
<lorddoskias>
okay, because with this one it didn't work
<lorddoskias>
though the check which emits that particular error message ought to be disabled
<fche>
module release vs. module version !!
<fche>
anyway I'd put the #ifndef line at translate.cxx line ... 1731ish
<fche>
and the #endif around ... 1765ish
<fche>
hm make that 1730 for the former, outside the { }
<fche>
dunno, whatever works syntactically, hiding the const char * release / version decls too
<lorddoskias>
yeah
<lorddoskias>
put it exactly on those lines just before you said it :D
<lorddoskias>
In function ‘systemtap_module_init’:
<lorddoskias>
/tmp/stapJDDurI/stap_125b0a3c53515242c8448b419e9ba101_1351_src.c:508: error: no return statement in function returning non-void
<lorddoskias>
hmz, commenting the wholoe code block just breaks it
<lorddoskias>
and it seems systemtap doesn't preserve the tmp files
<lorddoskias>
okay, testing with -k and then examining the code :)
<fche>
(or stap -p3)
<fche>
you'll have this working in no time
<lorddoskias>
hm, the generated code for systemtap_kernel_module_init does look really broken :D http://pastebin.com/Ssv8qAnU
<fche>
what a lovely no-op
<lorddoskias>
okay, did it :)
<lorddoskias>
so the verrel dif check has to be inside the code block :D
<lorddoskias>
fche: so if i send a patch would it be accepted :D ?
<fche>
why not.
<fche>
please make sure it's tested with and without that -D flag
<fche>
(an explicit test suite item would be wonderful too)
<fche>
(btw curious, for git commit name purposes, would you prefer Lord or Nikolay ?)
<lorddoskias>
Nikolay :D
<lorddoskias>
i still haven't had the chance to test the security scenario we discussed at FOSDEM
<lorddoskias>
;\
<lorddoskias>
but i think this won't be an issue because when stap is running in recorder mode, e.g. someone with a client can connect to an already running probe this would require access to the descriptor object on the hdd, right?
<lorddoskias>
(i have only skimmed the flight recorder documentation)
<fche>
yeah, the file descriptors are under /proc/systemtap somewhere
srikar_away is now known as srikar
<lorddoskias>
hm, i see no /proc/systemtap though when i have run a module as flight recorder
<fche>
could be /sys/kernel/debug/systemtap/ instead
<lorddoskias>
yep, it's there :)
<lorddoskias>
thanks
<lorddoskias>
righto, so if anyone wants to connect they need to have access to the debugfs in order to acquire the descriptor?
<fche>
and the kernel's sysfs file permissions widgetry would have to let them in
<irker366>
systemtap: dsmith systemtap.git:refs/heads/master * release-2.9-274-gde6d99c / testsuite/systemtap.examples/memory/hw_watch_addr.meta testsuite/systemtap.examples/memory/hw_watch_addr.tcl testsuite/systemtap.examples/memory/hw_watch_sym.meta testsuite/systemtap.examples/memory/hw_watch_sym.tcl: Better test for hardware breakpoint support in the examples. http://tinyurl.com/hgo5lv3