linux-kernel - Re: [00/17] Large Blocksize Support V3

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1177541179.32569.2.camel@dyn9047017100.beaverton.ibm.com>
Date:	Wed, 25 Apr 2007 15:46:19 -0700
From:	Badari Pulavarty <pbadari@...il.com>
To:	clameter@....com
Cc:	lkml <linux-kernel@...r.kernel.org>, Mel Gorman <mel@...net.ie>,
	William Lee Irwin III <wli@...omorphy.com>,
	David Chinner <dgc@....com>,
	Jens Axboe <jens.axboe@...cle.com>,
	Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: [00/17] Large Blocksize Support V3

On Tue, 2007-04-24 at 15:21 -0700, clameter@....com wrote:
> V2->V3

Hmm.. It broke ext2 :(

V2 worked fine with the small fix I sent you earlier.
But on V3, I can't run fsx. I see random data showing up.
I will debug, when I get a chance.

Thanks,
Badari

READ BAD DATA: offset = 0x5092a4, size = 0x5093a0, fname = (null)
OFFSET  GOOD    BAD     RANGE
0x77f466d0      0x77e1f7c0      0x0000  0x  6ef
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  6f1
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  6f1
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  6f3
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  6f3
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  6f5
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x776f6e6b      0x6b636568      0x0000  0x  84f
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  851
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  851
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  853
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  853
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  855
operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
0x776f6e6b      0x6b636568      0x0000  0x  857
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  859
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  859
operation# (mod 256) for the bad data may be 5284080
0x2820236e      0x77e1f7c0      0x0000  0x  85b
operation# (mod 256) for the bad data may be 5284080
LOG DUMP (49149 total operations):
0(2012505808 mod 256): WRITE    0x77f466d0 thru 0x77e1f7c0      (0x0
bytes) HOL***WWWW
0(2012505808 mod 256): WRITE    0x77f466d0 thru 0x77e1f7c0      (0x0
bytes)
0(2012505808 mod 256): READ     0x77f466d0 thru 0x77e1f7c0      (0x0
bytes)
0(2012505808 mod 256): READ     0x77f466d0 thru 0x77e1f7c0      (0x0
bytes)    ***RRRR***


-
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/