linux-ext4 - Re: [Fwd: [Bug] 2.6.30 kernel stack trace with 'fsfuzzer ext3' on s390]

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]

Date:	Mon, 29 Jun 2009 12:28:56 +0200
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Nageswara R Sastry <rnsastry@...ux.vnet.ibm.com>
Cc:	linux-ext4@...r.kernel.org, sachinp@...ux.vnet.ibm.com,
	linux-s390@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [Fwd: [Bug] 2.6.30 kernel stack trace with 'fsfuzzer ext3' on
	s390]

On Mon, Jun 29, 2009 at 02:42:43PM +0530, Nageswara R Sastry wrote:
> Hitting the same bug with 2.6.31-rc1 on s390 arch.
>
>
> EXT3-fs error (device loop0): htree_dirblock_to_tree: bad entry in  
> directory #2: rec_len % 4 != 0 - offset=44, inode=12, rec_len=139,  
> name_len=10
> __log_wait_for_space: needed 256 blocks and only had 0 space available
> __log_wait_for_space: no way to get more journal space

Does this _only_ happen on s390? I would expect that this is not
architecture specific. Whatever fsfuzzer is doing.
--
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