linux-ext4 - Re: Possible ext4 corruption

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: <20090311004709.GC15229@mit.edu>
Date:	Tue, 10 Mar 2009 20:47:10 -0400
From:	Theodore Tso <tytso@....edu>
To:	Andreas Dilger <adilger@....com>
Cc:	Kevin Shanahan <kmshanah@...b.org.au>,
	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: Possible ext4 corruption - ACL related?

On Tue, Mar 10, 2009 at 06:38:45PM -0600, Andreas Dilger wrote:
> > Actually, it's a bit more complicated than that.  I should really add
> > a hook to debugfs to automate this, but... to find the block to grab,
> > you do this.   
> 
> [many complex steps deleted]
> 
> > So now we know that the block containing inode 867 is 65+54 = 119
> 
> Or you can use imap (which Ted probably wrote in the first place. :-)
> 
> debugfs: imap some/problem/file
> Inode 867 is part of block group 0
> 	located at block 119, offset 0x0180

<Blush>

OK, now I'm embarassed.  I had completely forgotten that I had already
implemented it.  

And to think I've been doing the hard way most of the time (i.e.,
using dc and doing the calculations manually :-)

	     	     	 	  - 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