From: Takashi Iwai Subject: Re: locking looks odd Date: Tue, 30 Aug 2016 16:20:34 +0200 Message-ID: References: <20160816210322.GD4466@var.home> <0fec7ab2-f72f-a27a-e82b-58642836db88@perex.cz> <20160820121205.GK4252@var.home> <20160826190212.GR5165@var> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 6B83E266BEE for ; Tue, 30 Aug 2016 16:20:36 +0200 (CEST) In-Reply-To: <20160826190212.GR5165@var> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Samuel Thibault Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org (Adding Alan to Cc) On Fri, 26 Aug 2016 21:02:12 +0200, Samuel Thibault wrote: > > Samuel Thibault, on Sat 20 Aug 2016 14:12:05 +0200, wrote: > > I'd just like to check something: do we agree that libasound must be > > thread-safe by default (otherwise it breaks the application assumption > > that it's thread-safe)? If so, then there are thread-safety bugs: > > Ok, now with the discussion on the portaudio list starting at > > https://lists.columbia.edu/pipermail/portaudio/2016-August/000599.html > > it seems the issue was in portaudio, which was hit by the locking > behavior change. Good to hear that it's been addressed in portaudio side. But I still wonder in which code path the deadlock was triggered. Can anyone give the stack traces of deadlocked (multi-)threads? thanks, Takashi