Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp568647imn; Wed, 3 Aug 2022 16:05:11 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vQcxyUU7xkJyF+qVXv17r9aZFXgCYnL/JI2ma/TgDRa5bDCm7DAzChPD74X2QxmczBGYQe X-Received: by 2002:a05:6a00:2906:b0:52a:bc7f:f801 with SMTP id cg6-20020a056a00290600b0052abc7ff801mr28257761pfb.49.1659567911644; Wed, 03 Aug 2022 16:05:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659567911; cv=none; d=google.com; s=arc-20160816; b=J+KLKbndjTT5LOK5qne/yEqwpFvXHmehFp5hLLR3AFZBcZdqSPWsUXlW9Ez+EQ534N TgUPtwsILdXRmwRw8vii+hw+zzG+xRygTpYeiSwFUYm6LnSSoQxE+1DBhux7ZuDrOXBB s0tTIE7HgtpW4St9c8uhkY1z5eRU6aFw7CDAYqdNMmJW/ck/xPNw4xMdQvRbM5hJneKV rmmzi8ksvLeG+fC01ODDIa1mF51/BY29X1etMDSHM+Qxo7cCnR07DPidiHzvCyFDZcCe mGv+OZDQeTjMzmVH4QqmweTLm5tbxuDp9+EmbNsopXZ9ESUAAEqcUGnd0rVZka9sIyEt MpBg== 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:subject:cc:to:from:date; bh=d8afmJfoKbns7QAiYNly/R6BPvvbWMjswiLmXXImBiQ=; b=lYzzXPJuv8+e5UYGQ9CXWzR5iNRKFkmoDnrmHs7fnqTZck273Zb6rfr1uka2BtVx8D HbkSrx7R478K1HMP7/p4gQwkFF9w9nHuiPyxovLXq+ta14rDqhzRBq1ifsC+3TRyevLh 0fa0bdLqQd4Taqp0Ed1qAwf/g1puMEGOfFe7eTuwYCshdGR7Qj4pxG+KJPPzyzXfy8Gx 7TdySNPR0z/4BobA3/X0cpJHJv4T8WPZOISROIILOp3/MJHwDlZTrDwZVdAjJ0U9Gdaq p/IuBjMIUEG1WiBwRTepJpw3N6N/o2iHeztWZgQ1FU0HYmQ6WXDOF2bZ5IhXRizz1pcm yNkg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j6-20020a17090ae60600b001f4ed654cdasi2807276pjy.109.2022.08.03.16.04.56; Wed, 03 Aug 2022 16:05:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236200AbiHCW7p (ORCPT + 99 others); Wed, 3 Aug 2022 18:59:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42368 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236800AbiHCW7n (ORCPT ); Wed, 3 Aug 2022 18:59:43 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D45321759F; Wed, 3 Aug 2022 15:59:41 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 805A3B8227F; Wed, 3 Aug 2022 22:59:40 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 72B09C433D6; Wed, 3 Aug 2022 22:59:38 +0000 (UTC) Date: Wed, 3 Aug 2022 18:59:36 -0400 From: Steven Rostedt To: Linus Torvalds Cc: Al Viro , Sebastian Andrzej Siewior , Thomas Gleixner , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [git pull] vfs.git pile 3 - dcache Message-ID: <20220803185936.228dc690@gandalf.local.home> In-Reply-To: References: X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 3 Aug 2022 15:09:23 -0700 Linus Torvalds wrote: > Admittedly I think "preempt_enable_under_spinlock()" may be a bit > *too* cumbersome as a name. It does explain what is going on - and > both the implementation and the use end up being fairly clear (and the > non-RT case could have some debug version that actually tests that > preemption has already been disabled). preempt_disable_inlock() ? -- Steve