From: Christoph Hellwig <hch@infradead.org>
To: Peng Tao <bergwolf@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Christoph Hellwig <hch@infradead.org>,
"Dilger, Andreas" <andreas.dilger@intel.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH] staging: Disable lustre file system for MIPS, SH, and XTENSA
Date: Wed, 11 Sep 2013 09:29:55 -0700 [thread overview]
Message-ID: <20130911162955.GA1103@infradead.org> (raw)
In-Reply-To: <CA+a=Yy7+cj4Bw_4PArxMo2Manqp+aTVUi-7UcS+6-qNv7-RPyA@mail.gmail.com>
On Wed, Sep 11, 2013 at 10:51:50AM +0800, Peng Tao wrote:
> I'm not fighting against removing the piece of code. But if there is a
> strong reason to keep the functionality, we need to find a way to
> implement it. The convenience of using environment variables is that
> job scheduler can set the environment and other existing applications
> don't have to change. Are there other means to do the same? ioctl and
> upcall both need application change AFAIK.
There is no use case for it, the kernel has no business looking at these
variables. Given that you think it's not even used I don't even know
why we're having this discussion.
Talking about nasty code, the whole linux-curproc.c is highly
questionable:
- cfs_curproc_groups_nr:
unused and should be removed
- cfs_cap_raise/cfs_cap_lower/cfs_cap_raised:
needs to go away, modyules must not change access permissions
on behalf of processes
- the whole cfs_cap_t handling also needs to go away, passing around
capabilities is not a concept the kernel supports for a reason
- current_is_32bit:
Code should just use is_compat_task directly.
I've just taken the time to walk through this one file, but it seems
like most of libcfs is just as bad.
next prev parent reply other threads:[~2013-09-11 16:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 1:03 Guenter Roeck
2013-09-09 1:59 ` Greg Kroah-Hartman
2013-09-09 2:18 ` Ramkumar Ramachandra
2013-09-09 2:33 ` Greg Kroah-Hartman
2013-09-09 2:38 ` Ramkumar Ramachandra
2013-09-09 2:50 ` Greg Kroah-Hartman
2013-09-09 2:55 ` Ramkumar Ramachandra
2013-09-09 3:21 ` Guenter Roeck
2013-09-09 3:38 ` Ramkumar Ramachandra
2013-09-09 2:24 ` Guenter Roeck
2013-09-09 2:31 ` Greg Kroah-Hartman
2013-09-09 2:31 ` Guenter Roeck
2013-09-09 5:01 ` Heiko Carstens
2013-09-10 17:14 ` Peng Tao
2013-09-11 1:44 ` Christoph Hellwig
2013-09-11 2:25 ` Peng Tao
2013-09-11 2:30 ` Guenter Roeck
2013-09-11 2:51 ` Peng Tao
2013-09-11 16:29 ` Christoph Hellwig [this message]
2013-09-11 21:23 ` Dilger, Andreas
2013-09-11 20:48 ` Dilger, Andreas
2013-09-12 8:01 ` Peng Tao
2013-09-09 13:40 ` Christoph Hellwig
2013-09-09 16:39 ` Greg Kroah-Hartman
2013-09-09 17:08 ` Guenter Roeck
2013-09-09 17:22 ` Greg Kroah-Hartman
2013-09-09 19:11 ` Geert Uytterhoeven
2013-09-09 20:06 ` Guenter Roeck
2013-09-10 8:49 ` Geert Uytterhoeven
2013-09-10 16:44 ` Guenter Roeck
2013-09-10 16:51 ` Geert Uytterhoeven
2013-09-10 17:15 ` Peng Tao
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=20130911162955.GA1103@infradead.org \
--to=hch@infradead.org \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.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
all inboxes | Powered by JetHome®