Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp4809402imm; Tue, 26 Jun 2018 00:33:37 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIp0tH/lSZ/ozlqIlOLyllP2BRLkjtv+Rdv3pM1WW8jFKSfyHDzEjhd+6OZweMD5gjmuoZX X-Received: by 2002:a65:6689:: with SMTP id b9-v6mr372073pgw.326.1529998417128; Tue, 26 Jun 2018 00:33:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529998417; cv=none; d=google.com; s=arc-20160816; b=KGOM7+r6jr2tJEISQWW1RozvdqTAx/8FBOvWJ7oYGpHvbNWbRrRY3XO7EWIuB+uGl6 nxdPqoI6XM6N5M2GNwA7PTEDj0YSTjFqCIAanfxUGKsQPDTMeLGng+Xg1nVL8/Xbc41R ua8+UPxMzH5aKAArAO4eXFPxv1bDL1LkvCrmBD3g4RgP3Y0cMtdkGug8g05G9GwAYkKm lh1jZbDFhmxYaNgMw4Ska7h/I9ZPqALQ+ywi7K7XEeSzEqZ/CzHom2Lx0TSmnjgievhx hn0jaeIdDfXysWrmWrddJessw9f8PRlZKZz4hTojPI4oP+4EmHPkX+NYUQT846q8p9Yg l6Ng== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=wFKmCCMr/9QHxWFaodU87qz+JDdudOybdDbcl7nIgMg=; b=EwDc32t3y4T81CqmibGYHbdLUwlgjYdmjbEGnDjYNXq+er1SZ6RM6shla+amKj3RXN UXpLjrMJP0X8s3uyHpRqgYulCXDDjlPTWEXpvaibbOux0hAVePNCf4/PuzRnaWS1doT3 dF4w2qOjZvUVKGV91fesB+rq7b+JHVSTBD+pA6KgbO8pkGN72MkMP4U8eTGN0Zy8y70t svSoN6ONGUYJCkvWLiAsnTBt2IPVR4M1lShr1w/3vXTPCAd5/mTkQ1bfG+WfuvLBJnQ4 ofucEg+tgEz23gQuZNZlV1pTl5I84OH7+NIKeYKVvHI+r9sytplqS082WHursn3n+bxM Z8Kw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=Y1fxBcOw; 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 p5-v6si1035197pls.53.2018.06.26.00.33.22; Tue, 26 Jun 2018 00:33:37 -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=Y1fxBcOw; 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 S1752780AbeFZHbs (ORCPT + 99 others); Tue, 26 Jun 2018 03:31:48 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:52788 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752384AbeFZHbp (ORCPT ); Tue, 26 Jun 2018 03:31:45 -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-Transfer-Encoding :Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To: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=wFKmCCMr/9QHxWFaodU87qz+JDdudOybdDbcl7nIgMg=; b=Y1fxBcOwT69bh9vC6muPN0J6g8 9eQM+YCy8/CDmnKB/pb3mQlYtrx47VXpJfOwWwp3BsbQpO5XubgUb6ATozwQ0FAlFLPh8r0wk+9r+ X9XtSdfn7xcXjg2l414oU4m74B831a4L0Gz0UTElOuSnd+/rq3y//G3kTqKSxJBbieSnoHWefwb+s 4ArX1BeotSIM7YfKl9vlr5yI+AK+2Z/IWpBpWc5xeh/b5hsa40sKJhkmlzr2Hz2KQ07wsrkcnvqsa ExJsd81/6HHrzCVMEBF24WRw/PqCCdtligu48XGswwfEM1KYITg7lrwPUCxqQ5z0vcVo5IO2riNk8 Qnxr3JpQ==; 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 1fXiRs-0003AM-PR; Tue, 26 Jun 2018 07:31:37 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 1DB242029FA0E; Tue, 26 Jun 2018 09:31:34 +0200 (CEST) Date: Tue, 26 Jun 2018 09:31:34 +0200 From: Peter Zijlstra To: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Cc: linux-kernel@vger.kernel.org, Oleg Nesterov , "Eric W . Biederman" , "Rafael J . Wysocki" , Andrew Morton , Gavin Schenk , kernel@pengutronix.de Subject: Re: [PATCH] RFC: siox: don't create a thread without starting it Message-ID: <20180626073134.GW2458@hirez.programming.kicks-ass.net> References: <20180625102056.28468-1-u.kleine-koenig@pengutronix.de> <20180625125105.GZ2494@hirez.programming.kicks-ass.net> <20180625192121.k3hx32xbbhqkyfu4@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180625192121.k3hx32xbbhqkyfu4@pengutronix.de> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 25, 2018 at 09:21:21PM +0200, Uwe Kleine-K?nig wrote: > > > So I wonder where the real problem is and how it can be fixed. > > > > Without the first wakeup, the kthread will not run the provided function > > and we can therefore argue the creation is incomplete. I really feel you > > should just wake the thing up to land in your own wait-condition-loop. > Is this an ack for the RFC patch you replied to? Yes, Acked-by: Peter Zijlstra (Intel)