From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird name <SYSV00000000> ]
Date: Mon, 25 Feb 2013 14:27:49 +0000 [thread overview]
Message-ID: <20130225142749.GB4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+icZUXLO6MX==1zz1CUL+ytXv1bt+HjDx8Gug2p7GmfqtYBHw@mail.gmail.com>
On Mon, Feb 25, 2013 at 03:22:03PM +0100, Sedat Dilek wrote:
> On Mon, Feb 25, 2013 at 2:54 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > On Mon, Feb 25, 2013 at 02:22:42PM +0100, Sedat Dilek wrote:
> >
> >> [ 120.310366] Root dentry has weird name <SYSV00000000>
> >
> > Umm... Almost certainly a result of switching to shmem_file_setup() to
> > d_alloc_pseudo(); I'll fix it (give the suckers ->d_op of their own).
> > For now, just ignore the warning - it's harmless. Or revert commit
> > 7dbc68fcb0cdce27737dba9ee252f26d39d75fb6 and see if the rest of your
> > problems persist; I would be very surprised if anything other than this
> > warning had been caused by that commit.
>
> Thanks for the quick fix!
>
> YES, with "Revert "shmem_setup_file(): use d_alloc_pseudo() instead of
> d_alloc()"" I do NOT see these warnings anymore.
Umm... Are the perf ones you are seeing eliminated by that as well? I would
expect them to be an independent problem...
next prev parent reply other threads:[~2013-02-25 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 13:22 linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird name <SYSV00000000> ] Sedat Dilek
2013-02-25 13:49 ` Sedat Dilek
2013-02-25 13:54 ` Al Viro
2013-02-25 14:22 ` Sedat Dilek
2013-02-25 14:27 ` Al Viro [this message]
2013-02-25 14:35 ` Sedat Dilek
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=20130225142749.GB4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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.