Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1726509pxj; Sat, 12 Jun 2021 19:07:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJynCjHgKN8F+qEwisKkNpSsr5Btq7PZG1uNurz+6q3cDMrTUWp9UHm3oZtZh866SwhN6ozY X-Received: by 2002:a17:906:acf:: with SMTP id z15mr7387725ejf.140.1623550058463; Sat, 12 Jun 2021 19:07:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623550058; cv=none; d=google.com; s=arc-20160816; b=0NA2qbVu3cnONxzZnTLK+1iyB7UyhmhYlcJNBqwA2c4nkFu7kZn6SlFMaRAkJxps7x +Dohs8Ii+Hs79zfdCedSOHi6W7yXdMpxxsGNeykDC1BGY8CTltW/eaDr4AnVpYwctX6G wCxpXipo048Z0qdfFRaJ9/5IHv29BgKUU5dWTNGv7gww6k1oa4YSht4FbmTQRK+Mjdom AJKIKi+3Qy9dw5lOo7yWf8OVo4NeknU8cq20TSqT0xjoMH5Bor5U4Ki+youegksaV0Q3 AVJoeUGONxd82gllghndqkQH5aJle81gVjKTtCdXJhHqJ6kriBa3dxrztCmb/WxXvJN3 T5ow== 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 :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature:dkim-signature; bh=Uom0PmQvH9twYv18/8DY+8ughWYvRfkhlllMXqiZF9U=; b=oJI6y99oACkl1EDzgZkkyIOQrKTbmAkYIhtnXLgrXIdVgUifXu6IKvQ4Wla+hcMtRT tUzXerKEQB+Scuh0bplGRlTZwFnM9my0cqMw70JsZ9cRDxLrTOk6JR45XgSiCo5zms4l nI3c2DpxhjRYZ9g+0JorbjzFTzIRvSmUigFtnLa77CUw8bCSbIZj00cYSjvBj6lFexRR J2G0D+Ifdg4pBExKsT6BwAfuvG+JYBgoNEgK7ytFeAsU/z5evrW6USheQskMeqKl8lvP PRv+gavTyvodyoE/oMROfHpWo4dqrK2LGJ3DzjweCjra3jjO+5DH9+wlyHu4z8JDR1jB hbiA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@themaw.net header.s=fm3 header.b=OVUqdN8g; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=HNfZq2tl; 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 dd18si7929948edb.445.2021.06.12.19.06.50; Sat, 12 Jun 2021 19:07:38 -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; dkim=pass header.i=@themaw.net header.s=fm3 header.b=OVUqdN8g; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=HNfZq2tl; 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 S231597AbhFMB7W (ORCPT + 99 others); Sat, 12 Jun 2021 21:59:22 -0400 Received: from wnew3-smtp.messagingengine.com ([64.147.123.17]:49119 "EHLO wnew3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229985AbhFMB7V (ORCPT ); Sat, 12 Jun 2021 21:59:21 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.west.internal (Postfix) with ESMTP id 3D3644D0; Sat, 12 Jun 2021 21:57:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 12 Jun 2021 21:57:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=themaw.net; h= message-id:subject:from:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; s=fm3; bh= Uom0PmQvH9twYv18/8DY+8ughWYvRfkhlllMXqiZF9U=; b=OVUqdN8gDqbMKH0g IlIvGy0J1ex1TF/hXzLNtxTfLsNa4rSJkveblDtecrR9zYUHKgfiZi2GLyQz8khL yd881w21Mb6sfk6IE/KYPowxeh4lqcc+oROudNGRpZjeAHG3I0SyoGaRbaYjVC0q 50SaI6zRhbg7ILd3am82bbrnfAmCP74Xb/TgwwMR4b+6jE3YHoxN4AMAHelbDLeU vOnv8/qo1br9kMoxZ/A2S15L61yGXhXnxM1HS0mgpeDsYPJcGb+7vXwK4IKx2Nk7 x9wbNylHNp2CFyoBhyjtx556ET2k7pe9Gw5AwTnf51bA26pivVzgN1pgcIIUIqUa e8wpYw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=Uom0PmQvH9twYv18/8DY+8ughWYvRfkhlllMXqiZF 9U=; b=HNfZq2tlph76QK1wHJxNX6QbI4L3TFJBIjObPCmEcRhDEw5jUGAi/vz7y DkRRI4+vEj6TviS+s5KeBwcaN65Bl9bAUwQvebCw7IdodA47vAl7866a1bXizA2M p2JKl5jgV03coqHIecWwZx4qYUbTDRupWx+8skwYbR93eX/Y5JAlXloKUSYq9bv/ lB2C6LRi4MYTyLgs9V1KAfYeMT6YM/wFM+8dcXUEJFtQXwurUKzwtTu4zoXLwxBw RewV03ncFGxnl7QzafuquIQ6NX2ON35qZQ/SG/sVRVgu3GHqKJW9r2yhZfb9/3CJ qEh1uExBTKXSsas6ohBXJEpB6xe6g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvuddggeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkffuhffvffgjfhgtfggggfesthekredttderjeenucfhrhhomhepkfgrnhcu mfgvnhhtuceorhgrvhgvnhesthhhvghmrgifrdhnvghtqeenucggtffrrghtthgvrhhnpe fgleelkeetheelgeehueejueduhfeufffgleehgfevtdehhffhhffhtddugfefheenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehrrghvvghnse hthhgvmhgrfidrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 12 Jun 2021 21:57:14 -0400 (EDT) Message-ID: <8304e49310b16b865868982802bd2344d076c974.camel@themaw.net> Subject: Re: [PATCH v6 3/7] kernfs: use VFS negative dentry caching From: Ian Kent To: Al Viro Cc: Greg Kroah-Hartman , Tejun Heo , Eric Sandeen , Fox Chen , Brice Goglin , Rick Lindsley , David Howells , Miklos Szeredi , Marcelo Tosatti , "Eric W. Biederman" , Carlos Maiolino , linux-fsdevel , Kernel Mailing List Date: Sun, 13 Jun 2021 09:57:10 +0800 In-Reply-To: References: <162322846765.361452.17051755721944717990.stgit@web.messagingengine.com> <162322862726.361452.10114120072438540655.stgit@web.messagingengine.com> <2ee74cbed729d66a38a5c7de9c4608d02fb89f26.camel@themaw.net> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2021-06-12 at 01:51 +0000, Al Viro wrote: > On Sat, Jun 12, 2021 at 09:08:05AM +0800, Ian Kent wrote: > > > But if I change to take the read lock to ensure there's no > > operation > > in progress for the revision check I would need the dget_parent(), > > yes? > > WTF for?  ->d_parent can change *ONLY* when ->d_lock is held on all > dentries involved (including old and new parents). Understood, thanks. > > And it very definitely does *not* change for negative dentries.  I > mean, > look at the very beginning of __d_move().