linux-kernel - Re: [PATCH 5/5] Dump the inode structure (for debugging purposes only)

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090521202840.GB9236@mit.edu>
Date:	Thu, 21 May 2009 16:28:40 -0400
From:	Theodore Tso <tytso@....edu>
To:	Matthew Wilcox <matthew@....cx>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 5/5] Dump the inode structure (for debugging purposes
	only)

On Thu, May 21, 2009 at 02:09:42PM -0600, Matthew Wilcox wrote:
> On Thu, May 21, 2009 at 04:01:03PM -0400, Theodore Ts'o wrote:
> > This is not intended for merging; but it's useful for determining how
> > much varous fields in the struct inode space, and whether there is any
> > padding leading to waste, especially on a 64-bit platforms.
> 
> Why not just use acme's pahole?
> 

Because I didn't know about it, and now that I've looked at it, it
requires compiling the kernel with CONFIG_DEBUG_INFO, which means the
kernel takes a lot longer to build.  What I did is a bit more hackish,
to be sure, but it's faster to drop it into the tree and then run it
under kvm and then pull it out of the console logs.  If you were
planning on investigating a large number of structures, acme's
solution probably is a better one; but if you only need one, it might
be faster to whip up a custom kernel module, perhaps built out of the
tree, instead of rebuilding the entire kernel with CONFIG_DEBUG_INFO.

      	      	 	    	       	      - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/