Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2136829imu; Wed, 28 Nov 2018 23:20:41 -0800 (PST) X-Google-Smtp-Source: AFSGD/WcSXYsOa+BkCt6xTyHs+zpeqNsg4jRTTVROylRsniCN7a9Hf1GNprlPCPCMJyNRla7Wr8h X-Received: by 2002:a63:e001:: with SMTP id e1mr312930pgh.39.1543476041496; Wed, 28 Nov 2018 23:20:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543476041; cv=none; d=google.com; s=arc-20160816; b=u3zIFy2XDwcn1QiGV45vVGMVJgx7BsE4vTFVAyszWp2Nb/GHQOJ1GqmxgEt7OHNXbx NFKEIvcsfuxG3B4sEmO1ei32UzsFyQRG6PuYG4OFDX1/1KUiH3zn52tJtTbEE458XwxK AVOAD4CZBpO++GcSAjmh2ha+5CGrfSwLyjmp97+OAlXVjvKGv01r3HeV1+KZ6TkssoJQ XtnYKTbUpXpZCnkWvkZUx12TbkLUf5hJLvJwSLwc0PXLzv70KUrzqJjQsWxX8AVftlKY F8M9qQhr5Ahqb/bFAUz9cN0sMrVN/NBwC5GUW0qaCCvTgVtKggmLiiS3zTlZUV5s4H3f 9gvQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date; bh=wosLpb2ybRjBe2nOOXnIxtO0pRFx4QHjyStwJEULdAY=; b=cbh9FgnYfiIdWKzsMSR3Y/y5UwnzIanVVq01D42Si/MqRDbXRCLs+ozqffVrMplunF aWJi3s+frTA8mJQvLPMs9vmw+muaxo5SjpzH2xonfLo+qvxTCV2HiXaSG5OzCVYOO/W6 pw2546F0cJCfCW8MNJI1kMfvfjyndQIBWj7YAVZpjuoy2R4uwWmNjqLIEXPE7dXhwFuT eiBzOyOkqFsyXY4dv2ZGu7KYgWgIwPn1r7X0yzzrHNeXGCYrnArLUf2Ruy8aJ6UZQW/w wNe4d38RGznQbbUbfC6b6+2C+asCIYCgnbrEQBpIqL//uFwY6XrtXXH2KuOivAuAwD3m isRw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 66si1197414plc.125.2018.11.28.23.20.26; Wed, 28 Nov 2018 23:20:41 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727814AbeK2SYO (ORCPT + 99 others); Thu, 29 Nov 2018 13:24:14 -0500 Received: from mx2.suse.de ([195.135.220.15]:51458 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727666AbeK2SYO (ORCPT ); Thu, 29 Nov 2018 13:24:14 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id A42CBADE0; Thu, 29 Nov 2018 07:19:48 +0000 (UTC) Date: Thu, 29 Nov 2018 08:19:48 +0100 Message-ID: From: Takashi Iwai To: "Chanho Min" Cc: "'Jaroslav Kysela'" , "'Takashi Iwai'" , "'Vinod Koul'" , "'Daniel Mentz'" , , , "'Seungho Park'" , "'Jongsung Kim'" , "'Wonmin Jung'" , "'Jaehyun Kim'" , "'Hyonwoo Park'" Subject: Re: [PATCH] ALSA: pcm: Fix starvation on down_write_nonblock() In-Reply-To: <046401d48774$d7d1e440$8775acc0$@lge.com> References: <1543210597-6717-1-git-send-email-chanho.min@lge.com> <1aaf01d486ab$8017a5b0$8046f110$@lge.com> <046401d48774$d7d1e440$8775acc0$@lge.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/26 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 29 Nov 2018 00:48:20 +0100, Chanho Min wrote: > > > > > On Mon, 26 Nov 2018 06:36:37 +0100, > > > > Chanho Min wrote: > > > > > > > > > > Commit 67ec1072b053 ("ALSA: pcm: Fix rwsem deadlock for non-atomic > > > > > PCM > > > > > stream") fixes deadlock for non-atomic PCM stream. But, This patch > > > > causes antother stuck. > > > > > If writer is RT thread and reader is a normal thread, the reader > > > > > thread will be difficult to get scheduled. It may not give chance > > > > > to release readlocks and writer gets stuck for a long time if they > > > > > are > > > > pinned to single cpu. > > > > > > > > > > The deadlock described in the previous commit is because the linux > > > > > rwsem queues like a FIFO. So, we might need non-FIFO writelock, > > > > > not non- > > > > block one. > > > > > > > > > > My suggestion is that the writer gives reader a chance to be > > > > > scheduled by using the minimum msleep() instaed of spinning > > > > > without blocking by writer. Also, The *_nonblock may be changed to > > > > > *_nonfifo appropriately > > > > to this concept. > > > > > In terms of performance, when trylock is failed, this minimum > > > > > periodic msleep will have the same performance as the tick-based > > > > schedule()/wake_up_q(). > > > > > > > > > > Suggested-by: Wonmin Jung > > > > > Signed-off-by: Chanho Min > > > > > > > > Hrm, converting unconditionally with msleep() looks too drastic. > > > > > > Yes, it looks drastic. But, IMHO, I can't say busy-spin is not non- > > drastic. > > > To fix the root cause, We may need another rwsem that does not work as > > > a FIFO. > > > > Right, but applying msleep(1) unconditionally is really bad. > > > > > > I guess you've hit this while not explicitly using the linked PCM > > > > streams, i.e. in the call of snd_pcm_unlink() at close, right? > > > > > > > > Then this can be worked around by checking the link before calling it. > > > > Could you check the patch below? > > > > > > More testing is needed, but it seems to be fixed by your patch. > > > We may not use the linked PCM. > > > > Then I'm sure that my patch papers over. > Thanks, Plz let me know when the patch is merged. I'm going to merge the patch below now. It slips from the pull request to Linus in today, but will be the next one for 4.20-rc6. > > > But, If the linked PCM is enabled, Can snd_pcm_unlink() be called? > > > This also seems to be a workaround. > > > > Yes, for the linked streams, something else is needed *in addition*. > > > > The original fix with busy loop also assumed that this code path (via > > snd_pcm_link() and snd_pcm_unlink()) is the rare occasion, and it didn't > > consider that it were called for regular use cases. So the fix to make > > things just works for regular use cases without any artifact must be > > implemented in the first place. The fix for the linked streams comes at > > next. It might be like your msleep() change as a workaround, but in > > anyway it's far less urgency. > > msleep is worst, but If it is harmless, can I apply my patch to the private > tree > temporarily until your next fix comes? > We may use the linked streams in the near future. It makes our product > unstable. > It's urgency for us. How is your opinion? I'll add your fix on top of mine for now. The msleep() is applied only for linked streams, so it's not that bad any longer. thanks, Takashi -- 8< -- From: Takashi Iwai Subject: [PATCH] ALSA: pcm: Call snd_pcm_unlink() conditionally at closing Currently the PCM core calls snd_pcm_unlink() always unconditionally at closing a stream. However, since snd_pcm_unlink() invokes the global rwsem down, the lock can be easily contended. More badly, when a thread runs in a high priority RT-FIFO, it may stall at spinning. Basically the call of snd_pcm_unlink() is required only for the linked streams that are already rare occasion. For normal use cases, this code path is fairly superfluous. As an optimization (and also as a workaround for the RT problem above in normal situations without linked streams), this patch adds a check before calling snd_pcm_unlink() and calls it only when needed. Reported-by: Chanho Min Cc: Signed-off-by: Takashi Iwai --- sound/core/pcm_native.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sound/core/pcm_native.c b/sound/core/pcm_native.c index 66c90f486af9..6afcc393113a 100644 --- a/sound/core/pcm_native.c +++ b/sound/core/pcm_native.c @@ -2369,7 +2369,8 @@ int snd_pcm_hw_constraints_complete(struct snd_pcm_substream *substream) static void pcm_release_private(struct snd_pcm_substream *substream) { - snd_pcm_unlink(substream); + if (snd_pcm_stream_linked(substream)) + snd_pcm_unlink(substream); } void snd_pcm_release_substream(struct snd_pcm_substream *substream) -- 2.19.1