linux-kernel - Stuck in iowait regression in 3.18.1

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

Date:	Tue, 23 Dec 2014 16:31:21 +0100 (CET)
From:	Jonas Bofjäll <j-lnxk@...onk.org>
To:	linux-kernel@...r.kernel.org
Subject: Stuck in iowait regression in 3.18.1

After an uptime of a couple of days, I see some very strange i/o problems 
on Linux 3.18.1. The problem does not exist on 3.17.7 with identical 
configuration.

I originally had these problems running under VMware, using pvscsi, but I 
have since started seeing the same problems under KVM.

The process most likely to trip these problems are xz. The process gets 
stuck in iowait (D in ps) after having read or written a few hundred kB, 
almost every time it is run. The same thing has happened to a few other 
processes too (including sort and uniq), but the overwhelming majority 
work just fine.

The process _does_ get cputime eventually. A kill signal is honored in 
the time span of about an hour. Mostly. (Also, when working on reproducing 
the problem I once lost visibility of other terminal's processes under 
/proc. Could be related?)

I would like to bisect the 3.18 changes to see which one introduced this, 
but reproducing this takes several days. Any input or ideas how to hunt 
this down further?
--
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/