Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6113387yba; Tue, 14 May 2019 01:47:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqxa6ZnO2f+Rze2M2wEcnTEQIjVLS26IRhLdL25sA3/Kt2QsvdmMX7d0ZrWkh8ZYBdHKgqy5 X-Received: by 2002:a62:56d9:: with SMTP id h86mr40677180pfj.195.1557823632467; Tue, 14 May 2019 01:47:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557823632; cv=none; d=google.com; s=arc-20160816; b=nTp8p6tjWe+fNhgRh1x2FRKZfFcxR06hZUmBCcopqMV6uFAtQxUP13+r8z0Zm+g5La pUZrSKlKCHQGpXpCcvT0aYmmPAUtgJ72b0oqDRLPpY0EcNCo6TGYTkxm+NyYqU9xiw5f NUWhjmVjzokBqxN1bsXfNX43fhUu/salbhXLThF2uPkxF1lGT7ar5EgI+Ube4l9upPP0 Vr2P1K1xOz2VjpfQH/QNwP5nJT8/kTj0e07yYO67JmHgTu9LpeBVx/45VvpjnONK/xhN ZkxvJWeH+324mz0xMr9rPPC0qxA18Iz6J89iJu2vqM09cgbEAPN++BXdyIqIoZ2cLrZQ NAxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=ZFukSCaXEzzob4O1ASywHJ/kDWha8dAc33N1Kx8msEI=; b=R8n9m2Y+YW4WyNYxH9CJb8ZDR+JgSEQ8YJpQE2R03luQ0HDog/DjhJX377y3y4/B3O x7n7Sz3HqrL/4K034G871Zr0YyXxK5cGrfwpQozcJFHbqybuPPImevVRd3qTvdsetkgG myLzBt4ovrK93b696KqKiV9QS20HbBK7pQ7AotVJyrndKbyFfqDbxnei7c1Wsi6j7bcD xpeXWAHJF1txdDttXXgVrU03mGXfzY99nzskYeL1V0Vvt7oARO9FtfP1+4Sz+i4z6ptV GXpHaK86KjQQiABFFMVcweYt/LS+dXE4h2Ljb+ICU/PL4s5zbV+i6319Cfp+9qvsSTLC 1CoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=Jvnw4koa; 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 x21si5846121pfa.48.2019.05.14.01.46.57; Tue, 14 May 2019 01:47:12 -0700 (PDT) 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; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=Jvnw4koa; 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 S1726369AbfENIoI (ORCPT + 99 others); Tue, 14 May 2019 04:44:08 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:58436 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726007AbfENIoI (ORCPT ); Tue, 14 May 2019 04:44:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ZFukSCaXEzzob4O1ASywHJ/kDWha8dAc33N1Kx8msEI=; b=Jvnw4koacudV2mpSex+Jp9PVU u+p3BJnbpc+ernQ/5r/gu+G/f78E44NbLceEeuslh5phii0ZNJAnMFy//Yg55x1RWr011U6oq1+Ys Pl10ZvgyOygdKjQs0rlUJzQd+lsb14oxc/1h3f75GCZVFTvRmexCAfrMUKvLlCdHw4+j+hthkxuAS 50nhiDj/g2m+LIyoMwpCTI95tF652/74rS0OiUUQAFnt7fj78zaev08CHr7GsQrClv15G0X88Czsm t/E0BWT11XTbznL34YZPN8TuZBaH6gD3YMz9XwW0qMn/LibbMSiTRwh/cz7gTDC6SAgmGWmXT/Ual cmNWCij7w==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hQT2U-00069x-HM; Tue, 14 May 2019 08:43:58 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id D9B252029F87A; Tue, 14 May 2019 10:43:56 +0200 (CEST) Date: Tue, 14 May 2019 10:43:56 +0200 From: Peter Zijlstra To: Sebastian Andrzej Siewior Cc: minyard@acm.org, linux-rt-users@vger.kernel.org, Corey Minyard , linux-kernel@vger.kernel.org, tglx@linutronix.de, Steven Rostedt , Ingo Molnar Subject: Re: [PATCH RT v2] Fix a lockup in wait_for_completion() and friends Message-ID: <20190514084356.GJ2589@hirez.programming.kicks-ass.net> References: <20190508205728.25557-1-minyard@acm.org> <20190509161925.kul66w54wpjcinuc@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190509161925.kul66w54wpjcinuc@linutronix.de> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 09, 2019 at 06:19:25PM +0200, Sebastian Andrzej Siewior wrote: > On 2019-05-08 15:57:28 [-0500], minyard@acm.org wrote: > > kernel/sched/completion.c | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/kernel/sched/completion.c b/kernel/sched/completion.c > > index 755a58084978..4f9b4cc0c95a 100644 > > --- a/kernel/sched/completion.c > > +++ b/kernel/sched/completion.c > > @@ -70,20 +70,20 @@ do_wait_for_common(struct completion *x, > > long (*action)(long), long timeout, int state) > > { > > if (!x->done) { > > - DECLARE_SWAITQUEUE(wait); > > - > > - __prepare_to_swait(&x->wait, &wait); > > you can keep DECLARE_SWAITQUEUE remove just __prepare_to_swait() > > > do { > > + DECLARE_SWAITQUEUE(wait); > > + > > if (signal_pending_state(state, current)) { > > timeout = -ERESTARTSYS; > > break; > > } > > + __prepare_to_swait(&x->wait, &wait); > > add this, yes and you are done. > > > __set_current_state(state); > > raw_spin_unlock_irq(&x->wait.lock); > > timeout = action(timeout); > > raw_spin_lock_irq(&x->wait.lock); > > + __finish_swait(&x->wait, &wait); > > } while (!x->done && timeout); > > - __finish_swait(&x->wait, &wait); > > if (!x->done) > > return timeout; > > } Now.. that will fix it, but I think it is also wrong. The problem being that it violates FIFO, something that might be more important on -RT than elsewhere. The regular wait API seems confused/inconsistent when it uses autoremove_wake_function and default_wake_function, which doesn't help, but we can easily support this with swait -- the problematic thing is the custom wake functions, we musn't do that. (also, mingo went and renamed a whole bunch of wait_* crap and didn't do the same to swait_ so now its named all different :/) Something like the below perhaps. --- diff --git a/include/linux/swait.h b/include/linux/swait.h index 73e06e9986d4..f194437ae7d2 100644 --- a/include/linux/swait.h +++ b/include/linux/swait.h @@ -61,11 +61,13 @@ struct swait_queue_head { struct swait_queue { struct task_struct *task; struct list_head task_list; + unsigned int remove; }; #define __SWAITQUEUE_INITIALIZER(name) { \ .task = current, \ .task_list = LIST_HEAD_INIT((name).task_list), \ + .remove = 1, \ } #define DECLARE_SWAITQUEUE(name) \ diff --git a/kernel/sched/swait.c b/kernel/sched/swait.c index e83a3f8449f6..86974ecbabfc 100644 --- a/kernel/sched/swait.c +++ b/kernel/sched/swait.c @@ -28,7 +28,8 @@ void swake_up_locked(struct swait_queue_head *q) curr = list_first_entry(&q->task_list, typeof(*curr), task_list); wake_up_process(curr->task); - list_del_init(&curr->task_list); + if (curr->remove) + list_del_init(&curr->task_list); } EXPORT_SYMBOL(swake_up_locked); @@ -57,7 +58,8 @@ void swake_up_all(struct swait_queue_head *q) curr = list_first_entry(&tmp, typeof(*curr), task_list); wake_up_state(curr->task, TASK_NORMAL); - list_del_init(&curr->task_list); + if (curr->remove) + list_del_init(&curr->task_list); if (list_empty(&tmp)) break;