From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 45C02C433F5 for ; Sun, 10 Apr 2022 22:13:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243069AbiDJWPy (ORCPT ); Sun, 10 Apr 2022 18:15:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56908 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229622AbiDJWPu (ORCPT ); Sun, 10 Apr 2022 18:15:50 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 6FD002F3; Sun, 10 Apr 2022 15:13:38 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 23A40ED1; Sun, 10 Apr 2022 15:13:38 -0700 (PDT) Received: from airbuntu (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 62E2C3F70D; Sun, 10 Apr 2022 15:13:35 -0700 (PDT) Date: Sun, 10 Apr 2022 23:13:25 +0100 From: Qais Yousef To: Greg KH Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org, Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= , Abhijeet Dharmapurikar , Dietmar Eggemann , Steven Rostedt , Peter Zijlstra , Ingo Molnar , Vincent Guittot , Thomas Gleixner , Sebastian Andrzej Siewior , Juri Lelli , Daniel Bristot de Oliveira , Kees Cook , Andrew Morton , "Eric W. Biederman" , Alexey Gladkov , "Kenta.Tada@sony.com" , Randy Dunlap , Ed Tsai , Valentin Schneider Subject: Re: [PATCH v3 2/2] sched/tracing: Report TASK_RTLOCK_WAIT tasks as TASK_UNINTERRUPTIBLE Message-ID: <20220410221325.fimxzpzg26zmmsiz@airbuntu> References: <20220120162520.570782-1-valentin.schneider@arm.com> <20220120162520.570782-3-valentin.schneider@arm.com> <20220409234224.q57dr43bpcll3ryv@airbuntu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/10/22 08:14, Greg KH wrote: > On Sun, Apr 10, 2022 at 12:42:24AM +0100, Qais Yousef wrote: > > +CC stable > > > > On 01/20/22 16:25, Valentin Schneider wrote: > > > TASK_RTLOCK_WAIT currently isn't part of TASK_REPORT, thus a task blocking > > > on an rtlock will appear as having a task state == 0, IOW TASK_RUNNING. > > > > > > The actual state is saved in p->saved_state, but reading it after reading > > > p->__state has a few issues: > > > o that could still be TASK_RUNNING in the case of e.g. rt_spin_lock > > > o ttwu_state_match() might have changed that to TASK_RUNNING > > > > > > As pointed out by Eric, adding TASK_RTLOCK_WAIT to TASK_REPORT implies > > > exposing a new state to userspace tools which way not know what to do with > > > them. The only information that needs to be conveyed here is that a task is > > > waiting on an rt_mutex, which matches TASK_UNINTERRUPTIBLE - there's no > > > need for a new state. > > > > > > Reported-by: Uwe Kleine-K�nig > > > Signed-off-by: Valentin Schneider > > > > Any objection for this to be picked up by stable? We care about Patch 1 only in > > this series for stable, but it seems sensible to pick this one too, no strong > > feeling if it is omitted though. > > > > AFAICT it seems the problem dates back since commit: > > > > 1593baab910d ("sched/debug: Implement consistent task-state printing") > > > > or even before. I think v4.14+ is good enough. > > > > > This is not the correct way to submit patches for inclusion in the > stable kernel tree. Please read: > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > for how to do this properly. > > Apologies. commit: 25795ef6299f07ce3838f3253a9cb34f64efcfae Subject: sched/tracing: Report TASK_RTLOCK_WAIT tasks as TASK_UNINTERRUPTIBLE I am interested in Patch 1 in this series as I know it impacts some Android 5.10 users. But this patch seems a good candidate for stable too since it was observed by a user (Uwe) and AFAICT the problem dates back to v4.14+ kernels. Suggested kernels: v4.14+. This has already been picked up by AUTOSEL for v5.15+ stable trees. Hope I got the process right this time. Thanks! -- Qais Yousef