Description of problem: It is useful to know what device and inode reads/writes occur on. With systemtap one can follow pointers to find that information. However, that is painful for the typical users to go through the chain of pointers to find the information. There are already functions in the vfs tapset that provide that the device and inode. There are git commits that add those variables to vfs.read, vfs.write, vfs.read.return, and vfs.write.return and adjust the examples to use them: http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=commit;h=44767f2025faf9cd9fed01ef5d328a2d470dbf1f http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=commit;h=f2b54492ed30003763833a5a5ac210790af60ec9 http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=commit;h=72dde18184542ab746869bce04869c43f2436217 http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=commit;h=6a1d90ee1b3471847ff11e74bc2cb19928f5de1a
is this in or out of 5.3? Having this would make the inode-watch example much simpler.
It's out - was not worth the disruption that a late rebuild could cause.
Is there going to be a respin of systemtap for 5.4?
*** This bug has been marked as a duplicate of bug 481377 ***