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  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]
Date:	Wed, 26 Jun 2013 23:39:49 -0400
From:	Eric Sandeen <>
To:	jon ernst <>
Subject: Re: "block_dump, bd" in debugfs

On 6/26/13 11:05 PM, jon ernst wrote:
> Hi, 
> When I use "block_dump" to dump certain block. I got 12288 bytes dumped.

output example?  It dumps a hexadecimal representation w/ octal
offsets, if you're counting bytes in the *text* output it'd be more than 4096.

> But I checked my block_size, it is 4k.
> At debugfs interactive prompt, it says "Dump contents of a block". So I am confused here. 
>  I read the code, it has    for (i=0; i<current_fs->blocksize; i+=16) ,I don't understand why I can get 12k output.

Each line represents 16 bytes worth of data, with the starting offset of each line in octal.

When I run it on nonrepeating data, line starting points go from 0000 to 7760 (octal) on a 4k block (so it ends at 07777, or offset 4095)

> Also at the beginning of each line. The output pattern is "0000, 0020, 0040, 0060, 0100, 0120", where are numbers such as"0080,"?

Identical lines are suppressed, similar to what hexdump does by default.  You might have had a "*" in between?

> Thanks in advance for any explanation.

I suppose manpage docs would help, but who has time to write those!  ;)

To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists