All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tejun Heo <tj@kernel.org>, Hou Tao <houtao1@huawei.com>,
	David Howells <dhowells@redhat.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Rick Lindsley <ricklind@linux.vnet.ibm.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Carlos Maiolino <cmaiolino@redhat.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernfs: don't create a negative dentry if inactive node exists
Date: Thu, 30 Sep 2021 06:50:56 +0800	[thread overview]
Message-ID: <32c970d1f93a02207cb1746852e51bae4b2691c8.camel@themaw.net> (raw)
In-Reply-To: <d54d122a7267eddbdcdeb4cb4fad6630e9e0ffe3.camel@themaw.net>

On Thu, 2021-09-30 at 06:28 +0800, Ian Kent wrote:
> On Wed, 2021-09-29 at 08:05 +0200, Greg Kroah-Hartman wrote:
> > On Wed, Sep 29, 2021 at 11:04:34AM +0800, Ian Kent wrote:
> > > In kernfs_iop_lookup() a negative dentry is created if there's no
> > > kernfs
> > > node associated with the dentry or the node is inactive.
> > > 
> > > But inactive kernfs nodes are meant to be invisible to the VFS
> > > and
> > > creating a negative dentry for these can have unexpected side
> > > effects
> > > when the node transitions to an active state.
> > > 
> > > The point of creating negative dentries is to avoid the expensive
> > > alloc/free cycle that occurs if there are frequent lookups for
> > > kernfs
> > > attributes that don't exist. So kernfs nodes that are not yet
> > > active
> > > should not result in a negative dentry being created so when they
> > > transition to an active state VFS lookups can create an
> > > associated
> > > dentry is a natural way.
> > > 
> > > Signed-off-by: Ian Kent <raven@themaw.net>
> > > ---
> > >  fs/kernfs/dir.c |    9 ++++++++-
> > >  1 file changed, 8 insertions(+), 1 deletion(-)
> > 
> > Does this fix a specific commit and need a "Fixes:" tag?
> 
> Oh, of course yes, apologies, my bad.
> I re-post it.

But in case your ok to add it on my behalf it should be:
Fixes: c7e7c04274b1 ("kernfs: use VFS negative dentry caching")

> 
> 
> Ian



      reply	other threads:[~2021-09-29 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29  3:04 [PATCH] kernfs: don't create a negative dentry if inactive node exists Ian Kent
2021-09-29  6:05 ` Greg Kroah-Hartman
2021-09-29 22:28   ` Ian Kent
2021-09-29 22:50     ` Ian Kent [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32c970d1f93a02207cb1746852e51bae4b2691c8.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=cmaiolino@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=houtao1@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=ricklind@linux.vnet.ibm.com \
    --cc=tj@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.