linux-ext4 - Re: [PATCH] debugfs: fix printing of inline data during symlink inode dump

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 22 Jul 2014 18:44:18 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	"Darrick J. Wong" <darrick.wong@...cle.com>
Cc:	Andreas Dilger <adilger@...ger.ca>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] debugfs: fix printing of inline data during symlink
 inode dump

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@...cle.com>

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html