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: Tue, 31 Jan 2017 10:35:00 +0100 From: Takashi Iwai <tiwai@...e.de> To: Vlastimil Babka <vbabka@...e.cz> Cc: Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response On Mon, 30 Jan 2017 16:02:38 +0100, Vlastimil Babka wrote: > > On 01/25/2017 06:06 PM, Takashi Iwai wrote: > > The code path is related with the runtime PM, so it's likely depending > > on the device state, e.g. long-time pause or such. I don't think Win > > 10 plays a role, but who knows. > > > > In anyway, let me know if this helps. Basically I can merge it even > > for now, as the fix shouldn't give a regression. But of course it'd > > be better to have a test result :) > > OK so unfortunately it now happened with the patch. Hm, do you get the very same stack trace? It's strange because azx_rirb_get_response() has the timeout of 1 second in its loop, so it can't wait forever. Takashi
Powered by blists - more mailing lists