| 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
| ||
|
Date: Sat, 7 Jul 2007 09:56:30 +0200 From: Pavel Machek <pavel@....cz> To: Benjamin Herrenschmidt <benh@...nel.crashing.org> Cc: Alan Stern <stern@...land.harvard.edu>, Paul Mackerras <paulus@...ba.org>, Johannes Berg <johannes@...solutions.net>, "Rafael J. Wysocki" <rjw@...k.pl>, Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>, Kernel development list <linux-kernel@...r.kernel.org>, Matthew Garrett <mjg59@...f.ucam.org> Subject: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway Hi! > > How will that help? Block the kernel thread in the freezer or block it > > in the driver -- either way it is blocked. So how do your deadlocks > > get resolved? > > Because nobody is waiting on that kernel thread anyway without a freezer > so there is no deadlock anymore. In the deadlock we are seeing, _someone_ is waiting on userspace thread, that leads to deadlock with freezer. We don't know who, because we have not seen the sysrq-t dumps. The "unknown who" will deadlock on fused frozen by driver, too. We really need to fix the "unknown who" here. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/
Powered by blists - more mailing lists