[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUXLO6MX==1zz1CUL+ytXv1bt+HjDx8Gug2p7GmfqtYBHw@mail.gmail.com>
Date: Mon, 25 Feb 2013 15:22:03 +0100
From: Sedat Dilek <sedat.dilek@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird
name <SYSV00000000> ]
On Mon, Feb 25, 2013 at 2:54 PM, Al Viro <viro@...iv.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.
If you have a fix or sth. for testing, please let me know!
- Sedat -
View attachment "dmesg_3.8.0-next20130225-2-iniza-small_after-ffx-start.txt" of type "text/plain" (64668 bytes)
Download attachment "3.8.0-next20130225-2-iniza-small.patch" of type "application/octet-stream" (3104 bytes)
Powered by blists - more mailing lists