From: Christoph Hellwig <hch@infradead.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] vfs: add d_ancestor()
Date: Wed, 15 Oct 2008 15:53:18 -0400 [thread overview]
Message-ID: <20081015195318.GA28349@infradead.org> (raw)
In-Reply-To: <e015bca83e848f5f6f2226623.ps@mail.parknet.co.jp>
On Wed, Oct 15, 2008 at 10:58:10PM +0900, OGAWA Hirofumi wrote:
>
>
> This adds d_ancestor() instead of d_isparent(), then use it.
>
> If new_dentry == old_dentry, is_subdir() returns 1, looks strange. But
> I'm not checking callers for now, so this keeps current behavior.
This change looks good, but a slightly more detailed changelog would be
good.
>
> /*
> - * Helper that returns 1 if p1 is a parent of p2, else 0
> + * Helper that returns the ancestor dentry of p2 which is a child of
> + * p1, if p1 is an ancestor of p2, else NULL.
> */
> -static int d_isparent(struct dentry *p1, struct dentry *p2)
> +struct dentry *d_ancestor(struct dentry *p1, struct dentry *p2)
Given that d_ancestor is non-static a kerneldoc comment describing it
instead of a plain one would be good.
> int is_subdir(struct dentry * new_dentry, struct dentry * old_dentry)
> {
> int result;
> - struct dentry * saved = new_dentry;
> unsigned long seq;
>
> + if (new_dentry == old_dentry)
> + return 1;
Maybe a comment like in your commit description here would be good?
> +
> /* need rcu_readlock to protect against the d_parent trashing due to
> * d_move
> */
> rcu_read_lock();
> do {
> /* for restarting inner loop in case of seq retry */
> - new_dentry = saved;
> - result = 0;
> seq = read_seqbegin(&rename_lock);
> - for (;;) {
> - if (new_dentry != old_dentry) {
> - if (IS_ROOT(new_dentry))
> - break;
> - new_dentry = new_dentry->d_parent;
> - continue;
> - }
> - result = 1;
> - break;
> - }
> + result = (d_ancestor(old_dentry, new_dentry) != NULL);
> } while (read_seqretry(&rename_lock, seq));
That's a big improvement, but with a better loop and fixing all the
formatting mess in the old code it could become even better:
/*
* Need rcu_readlock to protect against the d_parent trashing due to
* d_move.
*/
rcu_read_lock();
do {
/* for restarting inner loop in case of seq retry */
seq = read_seqbegin(&rename_lock);
if (d_ancestor(old_dentry, new_dentry))
result = 1;
else
result = 0;
} while (read_seqretry(&rename_lock, seq));
rcu_read_unlock();
Nice set of patches!
next prev parent reply other threads:[~2008-10-15 19:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 13:58 [PATCH 1/6] vfs: replace parent == dentry->d_parent by IS_ROOT() OGAWA Hirofumi
2008-10-15 13:58 ` [PATCH 2/6] vfs: add d_ancestor() OGAWA Hirofumi
2008-10-15 13:58 ` [PATCH 3/6] vfs: add __d_instantiate() helper OGAWA Hirofumi
2008-10-15 13:58 ` [PATCH 4/6] vfs: remove unnecessary fsnotify_d_instantiate() OGAWA Hirofumi
2008-10-15 13:58 ` [PATCH 5/6] vfs: remove LOOKUP_PARENT from non LOOKUP_PARENT lookup OGAWA Hirofumi
2008-10-15 13:58 ` [PATCH 6/6] vfs: add LOOKUP_RENAME_NEW intent OGAWA Hirofumi
2008-10-15 19:37 ` Christoph Hellwig
2008-10-15 20:13 ` OGAWA Hirofumi
2008-10-15 19:44 ` [PATCH 5/6] vfs: remove LOOKUP_PARENT from non LOOKUP_PARENT lookup Christoph Hellwig
2008-10-15 21:43 ` OGAWA Hirofumi
2008-10-15 19:43 ` [PATCH 4/6] vfs: remove unnecessary fsnotify_d_instantiate() Christoph Hellwig
2008-10-15 20:16 ` OGAWA Hirofumi
2008-10-15 20:20 ` Christoph Hellwig
2008-10-15 19:41 ` [PATCH 3/6] vfs: add __d_instantiate() helper Christoph Hellwig
2008-10-15 20:39 ` OGAWA Hirofumi
2008-10-15 20:47 ` Trond Myklebust
2008-10-15 21:31 ` OGAWA Hirofumi
2008-10-15 19:53 ` Christoph Hellwig [this message]
2008-10-15 21:42 ` [PATCH 2/6] vfs: add d_ancestor() OGAWA Hirofumi
2008-10-15 19:45 ` [PATCH 1/6] vfs: replace parent == dentry->d_parent by IS_ROOT() Christoph Hellwig
2008-10-15 20:24 ` OGAWA Hirofumi
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=20081015195318.GA28349@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox