On Tue, Jul 22, 2014 at 01:47:52PM -0700, Darrick J. Wong wrote: > 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") > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> Applied, thanks. I had to make a minor change in your script to use $test_dir/image.gz instead of $test_name/image.gz. (The former doesn't work when the build directory != the source directory, i.e., when doing a VPATH build). - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
