linux-kernel - Re: Random freeze (Re: mmotm 2008-11-19-02-19 uploaded)

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: <5539.1227244998@turing-police.cc.vt.edu>
Date:	Fri, 21 Nov 2008 00:23:18 -0500
From:	Valdis.Kletnieks@...edu
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	penguin-kernel@...ove.sakura.ne.jp, linux-kernel@...r.kernel.org
Subject: Re: Random freeze (Re: mmotm 2008-11-19-02-19 uploaded)

On Thu, 20 Nov 2008 15:20:54 PST, Andrew Morton said:

> The traditional cause of the above trace is that someone mucked up the
> block/driver/irq-routing layer and we lost an IO completion.

Yes, that would explain all the symptoms and tracebacks - everybody comes
to a screeching halt the next time they try to go to disk, while the actual
disk drive is showing zero activity.

> It's also of course possible (but less common) that someone mucked up
> the VFS.  It would be interesting to revert
> do_mpage_readpage-dont-submit-lots-of-small-bios-on-boundary.patch.

I'm seeing an MTBF of about 2-3 hours when actually applying an I/O load to the
system.  I'll try reverting that patch, and if it survives an entire day or
two it will be pretty strong circumstantial evidence that patch is the culprit...

Content of type "application/pgp-signature" skipped