From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>
Subject: Re: [PATCH] staging/lustre: Replace jobid acquiring with per node setting
Date: Sun, 4 May 2014 00:15:24 -0400 [thread overview]
Message-ID: <20140504041524.GA3791@kroah.com> (raw)
In-Reply-To: <D18938B7-4D28-4312-8154-B5AE964ECEE4@linuxhacker.ru>
On Sat, May 03, 2014 at 11:08:36PM -0400, Oleg Drokin wrote:
> Hello!
>
> On May 3, 2014, at 10:33 PM, Greg Kroah-Hartman wrote:
> >> I don't think I saw complaints about proc files, the complaints I saw were mostly about
> >> reading env variables directly and the like so that was the focus of this patch.
> >> Did I miss some side discussion? Any pointers?
> > No, no side discussion, the proc files need to be removed / fixed before
> > the code can be merged to the "proper" part of the kernel tree.
>
> So, what's broken about them then?
> It's not like there are no files in proc or that lustre-proc files are causing some
> sort of breakage (at least not anymore after that recent patch).
The rule of not adding new proc files that do not relate to processes,
has been around for over a decade now, since 2.6.0 came out.
Please use sysfs instead, you can put your files in /sys/fs/lustre/ and
keep them to "one-value-per-file" files and document them in
Documentation/ABI/
thanks,
greg k-h
prev parent reply other threads:[~2014-05-04 4:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 2:21 [PATCH] staging/lustre: Replace jobid acquiring with per node setting Oleg Drokin
2014-05-03 23:29 ` Greg Kroah-Hartman
2014-05-04 1:20 ` Oleg Drokin
2014-05-04 2:33 ` Greg Kroah-Hartman
2014-05-04 3:08 ` Oleg Drokin
2014-05-04 4:15 ` Greg Kroah-Hartman [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=20140504041524.GA3791@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=green@linuxhacker.ru \
--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.