Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934153Ab3CMTK3 (ORCPT ); Wed, 13 Mar 2013 15:10:29 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:63108 "EHLO mail-we0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932526Ab3CMTK1 (ORCPT ); Wed, 13 Mar 2013 15:10:27 -0400 MIME-Version: 1.0 Reply-To: sedat.dilek@gmail.com In-Reply-To: <5140C77E.7030206@openwrt.org> References: <1363184193-1796-1-git-send-email-miklos@szeredi.hu> <20130313181251.GA6023@sgi.com> <5140C77E.7030206@openwrt.org> Date: Wed, 13 Mar 2013 20:10:25 +0100 Message-ID: Subject: Re: [PATCH 0/9] overlay filesystem: request for inclusion (v17) From: Sedat Dilek To: Felix Fietkau Cc: Robin Holt , Miklos Szeredi , viro@zeniv.linux.org.uk, torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, hch@infradead.org, akpm@linux-foundation.org, apw@canonical.com, neilb@suse.de, jordipujolp@gmail.com, ezk@fsl.cs.sunysb.edu, dhowells@redhat.com, sedat.dilek@googlemail.com, hooanon05@yahoo.co.jp, mszeredi@suse.cz Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1801 Lines: 45 On Wed, Mar 13, 2013 at 7:37 PM, Felix Fietkau wrote: > On 2013-03-13 7:12 PM, Robin Holt wrote: >> On Wed, Mar 13, 2013 at 05:51:33PM +0100, Sedat Dilek wrote: >>> On Wed, Mar 13, 2013 at 5:21 PM, Miklos Szeredi wrote: >>> > On Wed, Mar 13, 2013 at 5:10 PM, Sedat Dilek wrote: >>> > >>> >> Anyway, with CONFIG_OVERLAYFS_FS=m I do not see any related messages >>> >> when the kernel-module is loaded. >>> >> So, is this intended? >>> >> SquashFS prints into the logs, so what is it doing differently? >>> > >>> > Some modules do, some don't. It's not compulsory and not very useful. >>> > >>> >>> What about... >>> >>> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c >>> index 482c26f..92b9ad5 100644 >>> --- a/fs/overlayfs/super.c >>> +++ b/fs/overlayfs/super.c >>> @@ -675,11 +675,13 @@ MODULE_ALIAS_FS("overlayfs"); >>> static int __init ovl_init(void) >>> { >>> return register_filesystem(&ovl_fs_type); >>> + printk(KERN_INFO "overlayfs: loaded\n"); >> >> How about pr_debug(). That makes things quite for most of us but gives >> you info when looking for things like boot problems. > How is having a printk/pr_debug useful here at all? The fact that other > filesystems do this as well is not a good reason... > Also, putting it *after* the return statement doesn't make much sense ;) > Hehe, I just checked my new kernel... that does not work (nothing in the logs). But I think it's good to see if the filesystem is registered/loaded. - Sedat - > - Felix > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/