Received: by 2002:a05:6a10:c7c6:0:0:0:0 with SMTP id h6csp1639416pxy; Mon, 2 Aug 2021 06:51:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwIa0jM13s+CjAb6tT0CXVnsuCJs6fSXrXtw8N8T+uRSBPa9hD3RBC1Vc1Grkyh9SWCork6 X-Received: by 2002:a6b:f101:: with SMTP id e1mr1290047iog.118.1627912293668; Mon, 02 Aug 2021 06:51:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627912293; cv=none; d=google.com; s=arc-20160816; b=uNapWbKBEjvxo2fNTyl52fgYTHXiC45uvbDkFc6jCTX2ybrkbmy9JBhDRoKtFvvIL3 dq0eDp/7nre2ksySRzSmJV61WxgCt4gnuFT80+r01fyBSEmPBJBylRTrpn72HJ2UjT+2 mBTLZmWO3KJCI1aj4817aH/jW/d1HBZhq1YyThEnginocdtEZenqK5jkniltbEU3N74I B31gyLW8lmR7G7P2s5eiZG+Jd/EfpYozkmrSqIPoEUiglAQukeohix+p1wIoxnu34sfd BGIchp94c8FlQxbT0XAQ4ibxtKUnBShfKBcN8tmyK6fIbYyEjCT8Fv/wx7slzNU+OWJF F3Ew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=IkCtMKLMTMeCBqmlyyWVh8NrQ+1BImtl+Z+0LeDJtLY=; b=eFIaNBLlUIkMJPJ6jGSEBfIY9VFzcv6kuNA/9MIDpbzYjbvFYCF31rDaxtWYU+N3e6 lmJDWALTr4y7L+oVrzC86dzD58zDD0yDVeVAglJL9xUQHzxpZ6ZDWglX4LAlpzd68urq l6360O9kAk5Y972Mxgq5u5/AzqRU/+FF6MgG5ykPVY1PiVwc6gXdbRMJI/ywGXfywRy+ /0kR9k1xXqwVJcs4R7lTQIwV0SP9EmauXzKsgAaRmdR2Y1utBrmGE7FQhc325Si9ha8H 9GEH6KP7hJeYos/srejtezYSKPNVHLHOTqQYxSlAYFcQyQF6fprYjhrwdHunTEIxJUDu bnqg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o8si12489118iow.53.2021.08.02.06.51.20; Mon, 02 Aug 2021 06:51:33 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234506AbhHBNth (ORCPT + 99 others); Mon, 2 Aug 2021 09:49:37 -0400 Received: from szxga01-in.huawei.com ([45.249.212.187]:16035 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234378AbhHBNrg (ORCPT ); Mon, 2 Aug 2021 09:47:36 -0400 Received: from dggemv703-chm.china.huawei.com (unknown [172.30.72.53]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4GdfNf0m90zZwgx; Mon, 2 Aug 2021 21:43:46 +0800 (CST) Received: from dggpemm500006.china.huawei.com (7.185.36.236) by dggemv703-chm.china.huawei.com (10.3.19.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Mon, 2 Aug 2021 21:47:18 +0800 Received: from thunder-town.china.huawei.com (10.174.179.0) by dggpemm500006.china.huawei.com (7.185.36.236) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Mon, 2 Aug 2021 21:47:17 +0800 From: Zhen Lei To: Greg Kroah-Hartman , stable CC: Zhen Lei , Anna-Maria Gleixner , Mike Galbraith , Sasha Levin , Ingo Molnar , Peter Zijlstra , Thomas Gleixner , linux-kernel Subject: [PATCH 4.4 11/11] rcu: Update documentation of rcu_read_unlock() Date: Mon, 2 Aug 2021 21:46:24 +0800 Message-ID: <20210802134624.1934-12-thunder.leizhen@huawei.com> X-Mailer: git-send-email 2.26.0.windows.1 In-Reply-To: <20210802134624.1934-1-thunder.leizhen@huawei.com> References: <20210802134624.1934-1-thunder.leizhen@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.174.179.0] X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To dggpemm500006.china.huawei.com (7.185.36.236) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Anna-Maria Gleixner [ Upstream commit ec84b27f9b3b569f9235413d1945a2006b97b0aa ] Since commit b4abf91047cf ("rtmutex: Make wait_lock irq safe") the explanation in rcu_read_unlock() documentation about irq unsafe rtmutex wait_lock is no longer valid. Remove it to prevent kernel developers reading the documentation to rely on it. Suggested-by: Eric W. Biederman Signed-off-by: Anna-Maria Gleixner Signed-off-by: Thomas Gleixner Reviewed-by: Paul E. McKenney Acked-by: "Eric W. Biederman" Cc: bigeasy@linutronix.de Link: https://lkml.kernel.org/r/20180525090507.22248-2-anna-maria@linutronix.de Signed-off-by: Zhen Lei --- include/linux/rcupdate.h | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h index 0a93e9d1708e29e..3072e9c93ae6be2 100644 --- a/include/linux/rcupdate.h +++ b/include/linux/rcupdate.h @@ -880,9 +880,7 @@ static __always_inline void rcu_read_lock(void) * Unfortunately, this function acquires the scheduler's runqueue and * priority-inheritance spinlocks. This means that deadlock could result * if the caller of rcu_read_unlock() already holds one of these locks or - * any lock that is ever acquired while holding them; or any lock which - * can be taken from interrupt context because rcu_boost()->rt_mutex_lock() - * does not disable irqs while taking ->wait_lock. + * any lock that is ever acquired while holding them. * * That said, RCU readers are never priority boosted unless they were * preempted. Therefore, one way to avoid deadlock is to make sure -- 2.26.0.106.g9fadedd