Hi Tariq, First, please check the source code (ocfs2_trace.h) of your kernel module, how to define the related function trace. Second, you can send the reproduce steps to list, see if there is any issue. Third, since these trace entries are macro definitions, you can try to pre-compile the kernel module to see the real C code (or dis-assemble kernel module, more touch :-) ).
Thanks Gang >>> > Hi, > I apologize for using this list but no response to my query from > individual email. > There are trace calls like all over the code that seem to write into the > ftrace buffer. > trace_ocfs2_lookup(dir, dentry, dentry->d_name.len, > dentry->d_name.name, > (unsigned long long)OCFS2_I(dir)->ip_blkno, 0); > > But ftrace only shows fn name. No arguments. For example here is a > snippet from ls command. > ls-8932 [000] 10729002.743220: ocfs2_lookup <-do_lookup > ls-8932 [000] 10729002.743227: > ocfs2_inode_lock_full_nested <-ocfs2_lookup > > How do I get it to write args in the buffer and then display. > > Thank You. > -Tariq Saeed > > > _______________________________________________ > Ocfs2-devel mailing list > Ocfs2-devel@oss.oracle.com > https://oss.oracle.com/mailman/listinfo/ocfs2-devel _______________________________________________ Ocfs2-devel mailing list Ocfs2-devel@oss.oracle.com https://oss.oracle.com/mailman/listinfo/ocfs2-devel
