fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
<fche>
kerneltoast, reading
<fche>
interesting, how much testing did it survive?
orivej has joined #systemtap
<kerneltoast>
haven't done any heavy testing yet
<kerneltoast>
just lean testsuite stuff
<fche>
so this is all distinct from the inode-mutex business & bulk mode we were talking about yesterday
<fche>
anyway it looks plausible - using that lock as a proxy for reentrancy prevention too etc.
<fche>
so yeah interested in a fuller test run
<kerneltoast>
yep it's distinct
lijunlong has quit [Read error: Connection reset by peer]
lijunlong has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
orivej has quit [Ping timeout: 272 seconds]
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
orivej has joined #systemtap
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]