From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758399Ab3BYNyl (ORCPT ); Mon, 25 Feb 2013 08:54:41 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:55856 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756664Ab3BYNyj (ORCPT ); Mon, 25 Feb 2013 08:54:39 -0500 Date: Mon, 25 Feb 2013 13:54:36 +0000 From: Al Viro To: Sedat Dilek Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel Subject: Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird name ] Message-ID: <20130225135436.GA4503@ZenIV.linux.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 25, 2013 at 02:22:42PM +0100, Sedat Dilek wrote: > [ 120.310366] Root dentry has weird name 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.