linux-kernel - Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird name <SYSV00000000> ]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+icZUWh09aGsD25Xhx+WNWo65U7Wn6ydLZy1vep3hzecy5RyQ@mail.gmail.com>
Date:	Mon, 25 Feb 2013 15:35:54 +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 3:27 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
> 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@...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.
>
> Umm...  Are the perf ones you are seeing eliminated by that as well?  I would
> expect them to be an independent problem...

Independent as I still see them.
Please, see also my report in "Re: linux-next: Tree for Feb 23 [ perf:
NULL pointer dereference perf_init_event() ]" [1].

- Sedat -

[1] https://lkml.org/lkml/2013/2/25/119
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/