linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: hooanon05@yahoo.co.jp
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Q. DEBUG_FS and SYSFS config (Re: [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs)
Date: Tue, 24 Mar 2009 08:33:29 -0700	[thread overview]
Message-ID: <20090324153329.GA13705@kroah.com> (raw)
In-Reply-To: <2778.1237882600@jrobl>

On Tue, Mar 24, 2009 at 05:16:40PM +0900, hooanon05@yahoo.co.jp wrote:
> 
> Greg KH:
> > No one disables sysfs that I know of.  Heck, my phone enables sysfs...
> > 
> > > Addition to set limit, there is one more reason to adopt seq_file.
> > > Because the printed string is a path, it may contain unprintable
> > > characters. seq_file has a good interface seq_path() which supports
> > > escaping such characters.
> > 
> > That is true.  Ok, let's see the final result and I'll be glad to look
> > at it.
> 
> Hi Greg,
> 
> Currently I am testing locally about new aufs entries under debugfs, and
> I found a strange issue about configuration.
> 
> First, configure "normaly".
> General setup
>   [ ] Configure standard kernel features (for small systems)  --->
> 
> $ egrep -i '(sysfs|debug_fs)' .config
> CONFIG_SYSFS_DEPRECATED=y
> CONFIG_SYSFS_DEPRECATED_V2=y

You should disable those two options, no modern distro needs them
anymore.

> CONFIG_SYSFS=y
> CONFIG_DEBUG_FS=y
> # CONFIG_FAULT_INJECTION_DEBUG_FS is not set
> 
> Next, enable EMBEDED, and then disable SYSFS.
> General setup
>   [*] Configure standard kernel features (for small systems)  --->
> File systems
>   Pseudo filesystems  --->
>     [ ] sysfs file system support
> 
> $ egrep -i '(sysfs|debug_fs)' .config
> # CONFIG_SYSFS is not set
> CONFIG_DEBUG_FS=y
> 
> SYSFS is disabled expectedly, but DEBUG_FS is still enabled,
> while "depends on SYSFS" is specified for DEBUG_FS.
> 
> Is this expected behaviour?
> In other words, can I assume "when DEBUG_FS is enabled, SYSFS must be
> enabled too" safely?

Your code should not worry about either of these, it will "just work"
either way.

As for if there is a bug here, I don't know, the kbuild dependancies
should fix it up if you run "make oldconfig" right?

thanks,

greg k-h

  reply	other threads:[~2009-03-24 15:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  5:12 [RFC Aufs2 #3 0/2] 'debug' module parm and /sys/fs/aufs entries J. R. Okajima
2009-03-19  5:12 ` [RFC Aufs2 #3 1/2] replace /sys/fs/aufs/debug by /sys/module/aufs/parmaters/debug J. R. Okajima
2009-03-19  5:12 ` [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs J. R. Okajima
2009-03-20  0:45   ` Greg KH
2009-03-20  2:25     ` hooanon05
2009-03-20  2:42       ` Greg KH
2009-03-20  2:55         ` hooanon05
2009-03-20  3:06           ` Greg KH
2009-03-20  3:59             ` hooanon05
2009-03-20  4:18               ` Greg KH
2009-03-20  5:15                 ` hooanon05
2009-03-20  5:44                   ` Greg KH
2009-03-24  8:16                     ` Q. DEBUG_FS and SYSFS config (Re: [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs) hooanon05
2009-03-24 15:33                       ` Greg KH [this message]
2009-03-24 15:57                         ` Kay Sievers
2009-03-24 23:20                           ` Greg KH

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=20090324153329.GA13705@kroah.com \
    --to=greg@kroah.com \
    --cc=hooanon05@yahoo.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).