From: Christoph Lameter <clameter@sgi.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Greg KH <greg@kroah.com>, Latchesar Ionkov <lucho@ionkov.net>,
v9fs-developer@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/10] 9p: sysfs support for in-kenel servers
Date: Sat, 3 Nov 2007 11:22:03 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711031121250.5395@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1194085985.27652.409.camel@twins>
On Sat, 3 Nov 2007, Peter Zijlstra wrote:
> On Fri, 2007-11-02 at 20:48 -0700, Greg KH wrote:
>
> > Also, a sysfs file that causes an action to happen just by reading the
> > file is not a safe thing to have. Lots of scripts have been known to
> > just walk the whole sysfs tree and open and read everything they can for
> > no real good reason. So you should seriously reconsider this kind of
> > interaction.
>
> Christoph, doesn't SLUB do exactly that?
SLUB gathers statistics and summaries and displays them on read.
prev parent reply other threads:[~2007-11-03 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 17:05 [PATCH 7/10] 9p: sysfs support for in-kenel servers Latchesar Ionkov
2007-11-03 3:48 ` Greg KH
2007-11-03 10:33 ` Peter Zijlstra
2007-11-03 18:22 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0711031121250.5395@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=greg@kroah.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=peterz@infradead.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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).