Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 469188

Summary: vfs tapset enhancements
Product: Red Hat Enterprise Linux 5 Reporter: William Cohen <wcohen>
Component: systemtapAssignee: Frank Ch. Eigler <fche>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE <qe-baseos-auto>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3CC: mjw
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-02-17 17:29:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description William Cohen 2008-10-30 14:34:48 UTC 
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
Comment 1 William Cohen 2008-12-03 16:07:36 UTC 
is this in or out of 5.3? Having this would make the inode-watch example much simpler.
Comment 2 Frank Ch. Eigler 2008-12-03 16:15:16 UTC 
It's out - was not worth the disruption that a late rebuild could cause.
Comment 3 William Cohen 2009-02-16 21:36:30 UTC 
Is there going to be a respin of systemtap for 5.4?
Comment 4 Frank Ch. Eigler 2009-02-17 17:29:31 UTC 

*** This bug has been marked as a duplicate of bug 481377 ***