linux-kernel - [Regression] 2.6.24-git8 (and earlier): Multiple processes stuck in D states after logout from KDE

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

Date:	Wed, 30 Jan 2008 23:38:24 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [Regression] 2.6.24-git8 (and earlier): Multiple processes stuck in D states after logout from KDE

Hi,

Recently I've been observing problems with unmounting the /home fs on reboot
and/or shutdown on two test boxes.

After some more investigation I've found that this is due to some KDE processes
stuck in D states after their owner has logged out.

This happens 100% of the time if there's a suspend/resume cycle before the user
logs out (ie. the user logs into KDE, works for some time, suspends the box to
RAM and resmes one or more times and then logs out).  Still, I also observe the
symptoms on a box that's never suspended.

I'm not sure how to debug this, so please advise.

Thanks,
Rafael
--
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/