From: Greg KH <greg@kroah.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
Joel Becker <Joel.Becker@oracle.com>,
Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org,
Wim Coekaerts <wim.coekaerts@oracle.com>
Subject: Re: [Joel.Becker@oracle.com: Re: [Linux-cluster] Re: [PATCH 1/3] dlm: use configfs]
Date: Sun, 28 Aug 2005 15:48:26 -0700 [thread overview]
Message-ID: <20050828224826.GA29406@kroah.com> (raw)
In-Reply-To: <20050825174541.GA21228@ca-server1.us.oracle.com>
On Thu, Aug 25, 2005 at 10:45:42AM -0700, Mark Fasheh wrote:
> On Thu, Aug 25, 2005 at 11:58:19AM +0200, Christoph Hellwig wrote:
> > > > - there's still some procfs abuse
> > >
> > > Specifics of what is abuse vs OK would be interesting.
> >
> > You're using procfs for non-process data.
>
> I'm not sure I understand this... Looking through /proc I see lots of
> subsystems using /proc in similar ways to us. or is there a very specific
> method which you have a problem with?
No new subsystems or code shall add /proc files that do not explicitly
pertain to process information.
thanks,
greg k-h
next prev parent reply other threads:[~2005-08-29 8:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050822213220.GH19387@insight.us.oracle.com>
[not found] ` <20050822144521.24494329.akpm@osdl.org>
[not found] ` <20050822215049.GI19387@insight.us.oracle.com>
[not found] ` <20050822150505.7978136d.akpm@osdl.org>
2005-08-24 7:18 ` [Joel.Becker@oracle.com: Re: [Linux-cluster] Re: [PATCH 1/3] dlm: use configfs] Christoph Hellwig
2005-08-24 20:33 ` Joel Becker
2005-08-25 9:58 ` Christoph Hellwig
2005-08-25 17:45 ` Mark Fasheh
2005-08-28 22:48 ` Greg KH [this message]
2005-08-29 17:41 ` Joel Becker
2005-08-29 19:29 ` Miklos Szeredi
2005-08-31 6:14 ` Greg KH
2005-08-31 8:24 ` Joel Becker
2005-08-31 11:11 ` Miklos Szeredi
2005-08-25 18:45 ` Zach Brown
2005-08-25 20:23 ` Christoph Hellwig
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=20050828224826.GA29406@kroah.com \
--to=greg@kroah.com \
--cc=Joel.Becker@oracle.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=wim.coekaerts@oracle.com \
/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).