From: Miklos Szeredi <miklos@szeredi.hu>
To: Jeff Layton <jlayton@redhat.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] vfs: remove warning about "weird" root dentry name from prepend_path()
Date: Mon, 14 Jan 2013 16:50:20 +0100 [thread overview]
Message-ID: <CAJfpegujosQW8N6wTc_fxJ3BwVtJbBgat2YX9OJTMZEMqS40KQ@mail.gmail.com> (raw)
In-Reply-To: <1358175280-15903-1-git-send-email-jlayton@redhat.com>
On Mon, Jan 14, 2013 at 3:54 PM, Jeff Layton <jlayton@redhat.com> wrote:
> We've had several reports of this warning over the last year or so:
>
> [34011.669912] ------------[ cut here ]------------
> [34011.670473] WARNING: at fs/dcache.c:2630 prepend_path+0x1eb/0x200()
> [34011.671198] Hardware name: Bochs
> [34011.671564] Root dentry has weird name <> vfsmnt: fs:nfs4
[...]
> I'm able to reproduce this warning at will by mounting up a NFS
> filesystem, cd'ing into it. If I then lazy unmount the fs and then stat
> /proc/pid/cwd for the process sitting in the detached mount, this
> warning will fire.
>
> Given that this is fairly easy to reproduce without doing anything too
> exotic, I don't see much value in keeping this warning around.
The value of the warning is in preventing filesystems from doing weird
and exotic things without thinking about it.
The obvious question here is what is NFS4 doing differently from other
filesystems to trigger this warning and why.
Thanks,
Miklos
>
> Cc: Miklos Szeredi <miklos@szeredi.hu>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
> fs/dcache.c | 9 ---------
> 1 file changed, 9 deletions(-)
>
> diff --git a/fs/dcache.c b/fs/dcache.c
> index 19153a0..08a10a7 100644
> --- a/fs/dcache.c
> +++ b/fs/dcache.c
> @@ -2587,15 +2587,6 @@ out:
> return error;
>
> global_root:
> - /*
> - * Filesystems needing to implement special "root names"
> - * should do so with ->d_dname()
> - */
> - if (IS_ROOT(dentry) &&
> - (dentry->d_name.len != 1 || dentry->d_name.name[0] != '/')) {
> - WARN(1, "Root dentry has weird name <%.*s>\n",
> - (int) dentry->d_name.len, dentry->d_name.name);
> - }
> if (!slash)
> error = prepend(buffer, buflen, "/", 1);
> if (!error)
> --
> 1.7.11.7
>
next prev parent reply other threads:[~2013-01-14 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 13:59 WARNING: at fs/dcache.c:2630 prepend_path+0x1eb/0x200() Jeff Layton
2013-01-14 14:54 ` [PATCH] vfs: remove warning about "weird" root dentry name from prepend_path() Jeff Layton
2013-01-14 15:50 ` Miklos Szeredi [this message]
[not found] ` <20130114142458.0c509320@tlielax.poochiereds.net>
2013-01-15 0:18 ` Jeff Layton
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=CAJfpegujosQW8N6wTc_fxJ3BwVtJbBgat2YX9OJTMZEMqS40KQ@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).