On Fri, Mar 10, 2017 at 11:09:48AM -0800, Liu Bo wrote: > While debugging truncate problems, I found that these tracepoints could > help us quickly know what went wrong. > > Two sets of tracepoints are created to track regular/prealloc file item > and inline file item respectively, I put inline as a separate one since > what inline file items cares about are way less than the regular one. > > This adds four tracepoints: > - btrfs_get_extent_show_fi_regular > - btrfs_get_extent_show_fi_inline > - btrfs_truncate_show_fi_regular > - btrfs_truncate_show_fi_inline > > Cc: David Sterba <dsterba@xxxxxxx> > Signed-off-by: Liu Bo <bo.li.liu@xxxxxxxxxx> Reviewed-by: David Sterba <dsterba@xxxxxxxx> > + TP_PROTO(struct btrfs_inode *bi, struct extent_buffer *l, struct btrfs_file_extent_item *fi, u64 start), The 80-chars per line rule still applies, I've fixed them. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
