Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp1319947imm; Tue, 2 Oct 2018 06:29:12 -0700 (PDT) X-Google-Smtp-Source: ACcGV62b3IDJ3w0JfMX7Tuy5Dg6UHyBNxC8lP2lDR7C87ZjywtqmZKNOi2GMX3OjHYkqQf4ICd3Y X-Received: by 2002:a62:ff09:: with SMTP id b9-v6mr16301667pfn.46.1538486952171; Tue, 02 Oct 2018 06:29:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538486952; cv=none; d=google.com; s=arc-20160816; b=jrVbqRMxn7YS5TPPaaxC3tVgawkVSCI2cc2/VOpFIbQtun2RQc7/EjR27cCaHp2p4C RI090Vn5gMYWn22kcsTaa+YkgpVEbUCbylU6bMkYPuyloW4PyhQ7Obqjvf5/DQTVWpRW lVSZOYB5YGdLhN6gRWADwtxP4onCdp1zqxUURfk0RQe8lm0bCpbe6SSJoXyj1xxErQ7L vdB3VC3g2LwUl5gi8dZRUojNNrc4AMr9GdazzWX8Ljc/z1Mj8LZ+89BvkNB53urxtRd5 bf7xmpCsVgcL4+xbstmi+WlYKUG25dsmEgEAQ9QLkJMhU1RtCB9Lls6HXU3BW89kwUeA nXJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from; bh=4A3VHEZuXClTT/Ci31zZBSXm5Xfv0r0VVvXGYCalAAg=; b=aDRPaGonqHcQRgo0T7Wx3/ChUyAbnlrbyICaorKb645cCzs2YOkp6dXe0wEB9GCxOI 3NkrrW/Snk21EXqyLm/LWMYHJcLXlx96AyObGioqXO7l6ZDcMI30Q7JzTNQ1rFhRNCXZ bR9N/s1orgiKb1anKyXrPyhpq3vg5i8cSvjzauk70quGKwqOKaRkG/04vkCEf9GxYvUb YE42HK5c1126pg++NQ8VC4eskly0m2SMLOfp5AzXImBbtyAymd4kHWM1QeumjrMwBJZW +TwzXDoG/Nodf0QwihT4Xw4k6184ocCky5X5kv4yhLdn33R2T9gOKdO5YhySXJ8s0gx9 o/2A== 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 s21-v6si12881935pgj.90.2018.10.02.06.28.57; Tue, 02 Oct 2018 06:29: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; 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 S1728142AbeJBUK0 (ORCPT + 99 others); Tue, 2 Oct 2018 16:10:26 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:60094 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728078AbeJBUKZ (ORCPT ); Tue, 2 Oct 2018 16:10:25 -0400 Received: from localhost (24-104-73-23-ip-static.hfc.comcastbusiness.net [24.104.73.23]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id DB94FB2F; Tue, 2 Oct 2018 13:27:03 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, "Peter Zijlstra (Intel)" , =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= , Gavin Schenk , Sasha Levin Subject: [PATCH 4.18 006/228] siox: dont create a thread without starting it Date: Tue, 2 Oct 2018 06:21:43 -0700 Message-Id: <20181002132459.478244587@linuxfoundation.org> X-Mailer: git-send-email 2.19.0 In-Reply-To: <20181002132459.032960735@linuxfoundation.org> References: <20181002132459.032960735@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.18-stable review patch. If anyone has any objections, please let me know. ------------------ From: Uwe Kleine-König [ Upstream commit e890591413819eeb604207ad3261ba617b2ec0bb ] When a siox master device is registered a kthread is created that is only started when triggered by userspace. So this thread might be in TASK_UNINTERRUPTIBLE state for long and trigger a warning [ 241.130465] INFO: task siox-0:626 blocked for more than 120 seconds. with the respective debug settings enabled. It might be right to put an unstarted thread to TASK_IDLE (in kernel/kthread.c:kthread()) instead, but independant of this discussion it is cleaner for siox_master_register() to start the thread immediately. The effect is that it enters its own waiting state and then stays in state TASK_IDLE which doesn't trigger the above warning. As siox_poll_thread() uses some variables of the device the initialisation of these is moved before thread creation. Acked-by: Peter Zijlstra (Intel) Signed-off-by: Uwe Kleine-König Acked-by: Gavin Schenk Signed-off-by: Greg Kroah-Hartman Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- drivers/siox/siox-core.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) --- a/drivers/siox/siox-core.c +++ b/drivers/siox/siox-core.c @@ -715,17 +715,17 @@ int siox_master_register(struct siox_mas dev_set_name(&smaster->dev, "siox-%d", smaster->busno); + mutex_init(&smaster->lock); + INIT_LIST_HEAD(&smaster->devices); + smaster->last_poll = jiffies; - smaster->poll_thread = kthread_create(siox_poll_thread, smaster, - "siox-%d", smaster->busno); + smaster->poll_thread = kthread_run(siox_poll_thread, smaster, + "siox-%d", smaster->busno); if (IS_ERR(smaster->poll_thread)) { smaster->active = 0; return PTR_ERR(smaster->poll_thread); } - mutex_init(&smaster->lock); - INIT_LIST_HEAD(&smaster->devices); - ret = device_add(&smaster->dev); if (ret) kthread_stop(smaster->poll_thread);