From: hooanon05@yahoo.co.jp
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs
Date: Fri, 20 Mar 2009 14:15:49 +0900 [thread overview]
Message-ID: <6218.1237526149@jrobl> (raw)
In-Reply-To: <20090320041811.GA3352@kroah.com>
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).
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.
J. R. Okajima
next prev parent reply other threads:[~2009-03-20 5:16 UTC|newest]
Thread overview: 18+ 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 [this message]
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
2009-03-24 15:57 ` Kay Sievers
2009-03-24 15:57 ` Kay Sievers
2009-03-24 23:20 ` Greg KH
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=6218.1237526149@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.