linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, Ian Kent <raven@themaw.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Miklos Szeredi <mszeredi@suse.cz>
Subject: Re: [patch 2/6] fs: no games with DCACHE_UNHASHED
Date: Thu, 15 Oct 2009 10:13:43 +0200	[thread overview]
Message-ID: <20091015081343.GC4262@wotan.suse.de> (raw)
In-Reply-To: <4AD6D2E3.9050105@gmail.com>

On Thu, Oct 15, 2009 at 09:44:35AM +0200, Eric Dumazet wrote:
> npiggin@suse.de a écrit :
> > (this is in -mm)
> > 
> > Filesystems outside the regular namespace do not have to clear DCACHE_UNHASHED
> > in order to have a working /proc/$pid/fd/XXX. Nothing in proc prevents the
> > fd link from being used if its dentry is not in the hash.
> > 
> > Also, it does not get put into the dcache hash if DCACHE_UNHASHED is clear;
> > that depends on the filesystem calling d_add or d_rehash.
> > 
> > So delete the misleading comments and needless code.
> > 
> 
> This was added in commit 304e61e6fbadec586dfe002b535f169a04248e49
> 
>     [PATCH] net: don't insert socket dentries into dentry_hashtable
>     
>     We currently insert socket dentries into the global dentry hashtable.  This
>     is suboptimal because there is currently no way these entries can be used
>     for a lookup().  (/proc/xxx/fd/xxx uses a different mechanism).  Inserting
>     them in dentry hashtable slows dcache lookups.
>     
>     To let __dpath() still work correctly (ie not adding a " (deleted)") after
>     dentry name, we do :
>     
>     - Right after d_alloc(), pretend they are hashed by clearing the
>       DCACHE_UNHASHED bit.
>     
>     - Call d_instantiate() instead of d_add() : dentry is not inserted in
>       hash table.
>     
>       __dpath() & friends work as intended during dentry lifetime.
>     
>     - At dismantle time, once dput() must clear the dentry, setting again
>       DCACHE_UNHASHED bit inside the custom d_delete() function provided by
>       socket code, so that dput() can just kill_it.
>     
>     Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
>     Cc: Al Viro <viro@zeniv.linux.org.uk>
>     Acked-by: "David S. Miller" <davem@davemloft.net>
>     Signed-off-by: Andrew Morton <akpm@osdl.org>
>     Signed-off-by: Linus Torvalds <torvalds@osdl.org>
> 
> 
> 
> Back in 2006, we had to perform this hack in order to not leak '(deleted)' in __d_path()
> 
> if (!IS_ROOT(dentry) && d_unhashed(dentry) &&
> 	(prepend(&end, &buflen, " (deleted)", 10) != 0)) 
> 		goto Elong;
> 
> In current kernel this part became :
> 
> if (d_unlinked(dentry) &&
> 	(prepend(&end, &buflen, " (deleted)", 10) != 0))
> 		goto Elong;
> 
> 
> So your cleanup seems good, thanks !
> 
> Acked-by: Eric Dumazet <dada1@cosmosbay.com>

Ahh, hmm d_unlinked() is exactly the same code. OK, so I think this shows
why I'm an idiot. I didn't think about the __d_path output. Though the
comments are still misleading, in my defence (and my test programs did not
use any anoninode fds)...

Now both sockets and pipes define a d_dname so they are OK, but anon_inodes
does not. I think they should probably be made to just provide a d_dname
anyway so we can have the familiar format of "pseudofs:[ino]" rather than
"[pseudofs]" that we have now.

That should make this patch work for anon_inodes.c as well.

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-10-15  8:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15  4:40 [patch 0/6] vfsmount scaling and other bits npiggin
2009-10-15  4:40 ` [patch 1/6] fs: invalidate sb->s_bdev on remount,ro npiggin
2009-10-15  4:40 ` [patch 2/6] fs: no games with DCACHE_UNHASHED npiggin
2009-10-15  6:31   ` David Miller
2009-10-15  7:44   ` Eric Dumazet
2009-10-15  8:13     ` Nick Piggin [this message]
2009-10-15  8:29       ` Nick Piggin
2009-10-15  9:13         ` Eric Dumazet
2009-10-15 13:20         ` Matthew Wilcox
2009-10-15 14:41           ` Nick Piggin
2009-10-15  4:40 ` [patch 3/6] fs: dcache remove d_mounted npiggin
2009-10-15 10:37   ` Ian Kent
2009-10-15  4:40 ` [patch 4/6] brlock: introduce special brlocks npiggin
2009-10-15  6:58   ` [rfc][patch 4a/6] brlock: "fast" brlocks Nick Piggin
2009-10-15 11:05     ` Peter Zijlstra
2009-10-15 11:26       ` Nick Piggin
2009-10-19  5:25   ` [patch 4/6] brlock: introduce special brlocks Andrew Morton
2009-10-19  9:49     ` Nick Piggin
2009-10-19 12:24       ` Andrew Morton
2009-10-19 12:48         ` Nick Piggin
2009-10-15  4:40 ` [patch 5/6] fs: brlock vfsmount_lock npiggin
2009-10-15  4:40 ` [patch 6/6] fs: scale mntget/mntput npiggin

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=20091015081343.GC4262@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@suse.cz \
    --cc=raven@themaw.net \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).