From: ebiederm@xmission.com (Eric W. Biederman)
To: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Cc: al viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Revert "__d_unalias() should refuse to move mountpoints"
Date: Tue, 25 Sep 2012 04:29:58 -0700 [thread overview]
Message-ID: <87sja6nxvt.fsf@xmission.com> (raw)
In-Reply-To: <50618F96.1020204@canonical.com> (Maarten Lankhorst's message of "Tue, 25 Sep 2012 13:03:50 +0200")
Maarten Lankhorst <maarten.lankhorst@canonical.com> writes:
>> Could you try the following patch? This should report what directories
>> cannot be renamed because one of them is a mount point and it gives some
>> real insight into what is going on.
>
> ls /
> __d_unalias: /dev -> /dev
> __d_unalias: /proc -> /proc
> __d_unalias: /sys -> /sys
Ok. That is what I thought was going on. For some reason nfs is
attempting to recreate an existing dentry.
Does this fix the nfs problem for you?
Eric
diff --git a/fs/dcache.c b/fs/dcache.c
index 8086636..6390f0f 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -2404,6 +2404,9 @@ out_unalias:
if (likely(!d_mountpoint(alias))) {
__d_move(alias, dentry);
ret = alias;
+ } else if ((alias->d_parent == dentry->d_parent) &&
+ !dentry_cmp(alias, dentry->d_name.name, dentry->d_name.len))
+ ret = alias;
}
out_err:
spin_unlock(&inode->i_lock);
next prev parent reply other threads:[~2012-09-25 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 17:45 [PATCH] Revert "__d_unalias() should refuse to move mountpoints" Maarten Lankhorst
2012-09-25 3:39 ` Eric W. Biederman
2012-09-25 6:42 ` Maarten Lankhorst
2012-09-25 7:05 ` Eric W. Biederman
2012-09-25 9:04 ` Maarten Lankhorst
2012-09-25 10:42 ` Eric W. Biederman
2012-09-25 11:03 ` Maarten Lankhorst
2012-09-25 11:29 ` Eric W. Biederman [this message]
2012-09-25 11:59 ` Maarten Lankhorst
2012-10-12 13:25 ` Maarten Lankhorst
2012-11-29 20:06 ` Al Viro
2012-11-29 20:53 ` Al Viro
2012-11-29 21:30 ` Al Viro
2012-11-29 22:09 ` Al Viro
2012-12-04 10:33 ` Maarten Lankhorst
2012-12-04 10:37 ` Maarten Lankhorst
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=87sja6nxvt.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--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