linux-ext4 - Re: [bug] ext{3,4}: __find_get_block

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

Message-ID: <CANvSZQ8g5Wb7HwbCb7M9G+WQT0PK9nFSMWhybCza4xy+kOxAQA@mail.gmail.com>
Date:	Tue, 20 Sep 2011 20:08:29 +0200
From:	Thilo-Alexander Ginkel <thilo@...kel.com>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: [bug] ext{3,4}: __find_get_block_slow() failed on 3.0.3

On Mon, Sep 5, 2011 at 14:59, Jan Kara <jack@...e.cz> wrote:
>  Something has corrupted your buffer head structure in memory (and we then
> infinitely looped in __getblk_slow()). bh->b_blocknr has been 0xC139000B9
> which it should have been 0x139000B9 (5th byte has been changed from 0x00
> to 0x0C). It might be a hw fault, buggy driver, or some other bug - hard to
> say. You might want to run memtest for some time, or enable some kernel debug
> options (DEBUG_PAGEALLOC, DEBUG_SLAB) which might catch the code causing
> corruption (this assumes it's at least occasionally reproducible and your
> are willing to take the performance hit)...

Thanks for your reply and sorry for the slow response. As my system
also experienced lockups from time to time I performed an extensive
memtest run, which actually brought up sporadic memory corruption
(some bits flipping to zero) after 20 hours or so. I swapped CPU,
mainboard and RAM and have not experienced any problems since then, so
I guess this was the cause of the issue.

Thanks,
Thilo
--
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