tree 4504fb8dfe79983fbfff6fd5d84d3a29a45eb3ad
parent f9f3050a0ad9be1c37b00c8478199d286ddcaeda
author Darrick J. Wong <darrick.wong@oracle.com> 1406066513 -0400
committer Theodore Ts'o <tytso@mit.edu> 1406069073 -0400

debugfs: fix printing of inline data during symlink inode dump

When we're dumping a fast symlink inode, we print some odd things to
stdout.  To clean this up, first don't print inline data EA, since the
inode dump doesn't display file and directory contents.  Then, teach
the inode dump function how to print out either an inline data fast
symlink or a non-inline data fast symlink.

(This is a follow-up to the earlier patch "debugfs: Only print the
first 60 bytes from i_block on a fast symlink")

[ Modified by tytso so that the d_inline_dump test works when build
  directory is different from the source directory --- i.e., when
  doing a VPATH build. ]

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>