From: Greg KH <greg@kroah.com>
To: hooanon05@yahoo.co.jp
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs
Date: Thu, 19 Mar 2009 22:44:37 -0700 [thread overview]
Message-ID: <20090320054437.GC3993@kroah.com> (raw)
In-Reply-To: <6218.1237526149@jrobl>
On Fri, Mar 20, 2009 at 02:15:49PM +0900, hooanon05@yahoo.co.jp wrote:
>
> Greg KH:
> > Looks like a good start, if you are _sure_ you need sysfs files :)
>
> I believe those paths are important to users.
> When CONFIG_SYSFS is disabled, they are printed in /proc/mounts (and has
> severer limit).
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.
thanks,
greg k-h
next prev parent reply other threads:[~2009-03-20 5:47 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 [this message]
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
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=20090320054437.GC3993@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).