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 09FFEC76195 for ; Mon, 20 Mar 2023 17:58:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230366AbjCTR6D (ORCPT ); Mon, 20 Mar 2023 13:58:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51372 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229836AbjCTR5d (ORCPT ); Mon, 20 Mar 2023 13:57:33 -0400 Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 448BD20A33; Mon, 20 Mar 2023 10:52:20 -0700 (PDT) Received: by mail-qt1-x835.google.com with SMTP id r5so14091671qtp.4; Mon, 20 Mar 2023 10:52:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679334649; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:feedback-id:from:to:cc:subject:date :message-id:reply-to; bh=aQjkM9PKDL5Zc9X+NMDMWOfI4hV9Swlkx+f/dG2dChg=; b=NHZvq4NyIsQu/bi+Y0C7qiEnTDsnRv2Hza5qRUgyBE7ysLi9ulHO4V8FY4h6Habp4d Bvrn8eDqsJoNOyigPTSAHuNWtBRyCnk8YuipaPC4vNry5SWYj+H1eTemsrRco2fxm8M0 e4bfalj/k2MsF+ACl+sA8hxXZekOUIl9Rz2/VhDPcp+W9GgRKaXplvUAEWfybNaS2knQ agKo6sKxC5Vpl1RBgOyXK9evHdi2g+Tt6hOGkkvXHdz25CVff7CQ+juP/AdylQuWcjCJ lnDAq8E8/QWN1+jIaKttJ3bUixmG+mbP+SjTecvwVVDp7NpM8ZhqKn8AyBtH3AWQymcG pdCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679334649; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:feedback-id:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=aQjkM9PKDL5Zc9X+NMDMWOfI4hV9Swlkx+f/dG2dChg=; b=lodlJsUuab3A5IdbX50njI1O8+QD6kvFkYcjbgWeR8x6g97CGE69/7G+5QvxXsAe5V uGlDn4k3m19nj7yob3zBlKZXQW9ecmHnp8CyXjs9MiOHOSu0iF60gXVCTV79LrIaq3l1 6G81Yv5xJctBeH4BAE0HZCuEY9JMk3k8m/lJCx5X3BL3QCfE4K7EMdmIFNtXTpRcXYZp m9xLavkf3RVUrwY+BjSdTgXlxEdAU2F4vwZzPUFX2NPEhOlGq/EpCuHL0taz0SSadgxb nRrmvcrIqDHFLGnzPsQ2IrnEOAk9xpzZPirE82ZjWqNmIoNpuLoEW7p08njd4IRpNM14 3rvg== X-Gm-Message-State: AO0yUKUcbH16SpzEtqDxIYwf2g3EccuPLbFP01/k5DDdEIeYLOTm4009 GDOCsHMtVpfLXInGNqdIEl0= X-Google-Smtp-Source: AK7set9sgEJEikEBKPoxGLfLfLDV0IT4GGv9HZLouBThxSD+zT6GhvxJSpjZOowxWibHrwfR/6rr+w== X-Received: by 2002:a05:622a:15ce:b0:3b9:2c3:675a with SMTP id d14-20020a05622a15ce00b003b902c3675amr26957376qty.62.1679334649322; Mon, 20 Mar 2023 10:50:49 -0700 (PDT) Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com. [66.111.4.228]) by smtp.gmail.com with ESMTPSA id j185-20020a37b9c2000000b007465ad44891sm6730604qkf.102.2023.03.20.10.50.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Mar 2023 10:50:48 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailauth.nyi.internal (Postfix) with ESMTP id 345C927C0054; Mon, 20 Mar 2023 13:50:48 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 20 Mar 2023 13:50:48 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdefkedguddtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeeuohhq uhhnucfhvghnghcuoegsohhquhhnrdhfvghnghesghhmrghilhdrtghomheqnecuggftrf grthhtvghrnhephedugfduffffteeutddvheeuveelvdfhleelieevtdeguefhgeeuveei udffiedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epsghoqhhunhdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqieelvdeghedt ieegqddujeejkeehheehvddqsghoqhhunhdrfhgvnhhgpeepghhmrghilhdrtghomhesfh higihmvgdrnhgrmhgv X-ME-Proxy: Feedback-ID: iad51458e:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 20 Mar 2023 13:50:47 -0400 (EDT) Date: Mon, 20 Mar 2023 10:50:32 -0700 From: Boqun Feng To: Davidlohr Bueso Cc: rcu@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Will Deacon , Waiman Long , Lai Jiangshan , "Paul E. McKenney" , Josh Triplett , Steven Rostedt , Mathieu Desnoyers , Frederic Weisbecker , Neeraj Upadhyay , Joel Fernandes , Shuah Khan , David Woodhouse , Paolo Bonzini , kvm@vger.kernel.org, seanjc@google.com, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org Subject: Re: [PATCH rcu 1/7] locking/lockdep: Introduce lock_sync() Message-ID: References: <20230317031339.10277-1-boqun.feng@gmail.com> <20230317031339.10277-2-boqun.feng@gmail.com> <20230320170614.ttnqyhemnelgmzgd@offworld> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230320170614.ttnqyhemnelgmzgd@offworld> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 20, 2023 at 10:06:14AM -0700, Davidlohr Bueso wrote: > On Thu, 16 Mar 2023, Boqun Feng wrote: > > > +/* > > + * lock_sync() - A special annotation for synchronize_{s,}rcu()-like API. > > + * > > + * No actual critical section is created by the APIs annotated with this: these > > + * APIs are used to wait for one or multiple critical sections (on other CPUs > > + * or threads), and it means that calling these APIs inside these critical > > + * sections is potential deadlock. > > + * > > + * This annotation acts as an acqurie+release anontation pair with hardirqoff > ^acquire Good eye! Applied locally. Regards, Boqun