Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1436069ybh; Thu, 23 Jul 2020 08:52:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzdAW/ppnpyFi3d1TD7xnBXEeUCTjLi7Kdf06vVzWZr6K2RxlAQ0t+NScqP1QkbRXEMSzBA X-Received: by 2002:a17:906:8601:: with SMTP id o1mr5149692ejx.326.1595519539821; Thu, 23 Jul 2020 08:52:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595519539; cv=none; d=google.com; s=arc-20160816; b=tiQdctn5VDZu1W1mEedltS+clyEBBNU6QkBuAcLi88y61WrNAowDpqOf5xKTd6ZL+r +E0snGCdG6EGRk0TY+s8tgHP2wfSCcWd9JSp9gPZEzp7ikUOjXEhwC9P0sx702rmoBim 11u4+Lqf2vmRPW1eiUW5xDfJFdWzOLeFkM/ou/pvfbThV2LBV7eDUARHiUwm3uQbJneu HQkSLrpqodqGoAzjBK0/PAhdeIyz2r1zihlf99vCZeF5s4WDscHiCcxwrmx2xaOQ+XNU ok+HVHhezRXGth5d9VIuHf71bDTiIfuU+2fewKCA/miZ76rg3HCuYDe7RVCSQn8bbn+K 4tfw== 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; bh=1ndeJ/DwjzBXeA8nDjLH9C3Pxh9475xlLc/3G483TX0=; b=Fum0M2bth8X9UhmBe4WV39533ongzLd9rZgtzxa+gHQgBrR0oFRcDr5GL+M2ves+0C /55ScAxm7xZENbP3XWGpwlSp7G8LeBGg+SiHj5w3fre7fj3b2iOcqMoThs1daj1BtbyR 9kOdWVz4+XEVZZgl64LubDK6X3KWvXx76lbG0bC/K3/wqDbHQ94wrMhOXyjpmi22BJTI 1w1LHPCzJsfj4SuKVS3PuvhkidTHDVpF2JWYgSgmtRaMPyZaZkzQNF9J3pCVBVyprVJL YAD2ZLTYTkOO1KI689maUFGZi7dk0wdTIO5UdiS25Pw0NAR5bvUoMPXIFu6ZlzO8fc1P 4OLw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ao1si2191523ejc.575.2020.07.23.08.51.56; Thu, 23 Jul 2020 08:52:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729589AbgGWPvZ (ORCPT + 99 others); Thu, 23 Jul 2020 11:51:25 -0400 Received: from foss.arm.com ([217.140.110.172]:47906 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727108AbgGWPvY (ORCPT ); Thu, 23 Jul 2020 11:51:24 -0400 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 1FC831FB; Thu, 23 Jul 2020 08:51:24 -0700 (PDT) Received: from e107158-lin.cambridge.arm.com (e107158-lin.cambridge.arm.com [10.1.195.21]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 6DB4B3F66F; Thu, 23 Jul 2020 08:51:22 -0700 (PDT) Date: Thu, 23 Jul 2020 16:51:20 +0100 From: Qais Yousef To: Ingo Molnar , Peter Zijlstra Cc: Doug Anderson , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Patrick Bellasi , Chris Redpath , Lukasz Luba , linux-kernel@vger.kernel.org Subject: Re: [PATCH v7 3/3] sched/uclamp: Fix a deadlock when enabling uclamp static key Message-ID: <20200723155119.gs34voui4jx7cilb@e107158-lin.cambridge.arm.com> References: <20200716110347.19553-1-qais.yousef@arm.com> <20200716110347.19553-4-qais.yousef@arm.com> <20200716111328.zkhncw2aurrs4mad@e107158-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200716111328.zkhncw2aurrs4mad@e107158-lin.cambridge.arm.com> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/16/20 12:13, Qais Yousef wrote: > On 07/16/20 12:03, Qais Yousef wrote: > > [...] > > > Fix by ensuring we enable the key outside of the critical section in > > __sched_setscheduler() > > > > Fixes: 46609ce22703 ("sched/uclamp: Protect uclamp fast path code with static key") > > Signed-off-by: Qais Yousef > > I am assuming this Fixes tag is still valid given the patch is only in > tip/sched/core only. And that the hash value won't change after Linus merges > it. Gentle ping that this patch is actually a fix that I happened to uncover while testing this series. Happy to send separately. It should apply on its own too as it has no dependency on previous patches. Thanks -- Qais Yousef