mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Peng Tao <bergwolf@gmail.com>
Cc: 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: Tue, 10 Sep 2013 19:30:26 -0700	[thread overview]
Message-ID: <20130911023026.GA6273@roeck-us.net> (raw)
In-Reply-To: <CA+a=Yy6GFzoBT0Bgz7z5bHZRMdEBJa+txwpCZuxA+mRTch-8mA@mail.gmail.com>

On Wed, Sep 11, 2013 at 10:25:57AM +0800, Peng Tao wrote:
> On Wed, Sep 11, 2013 at 9:44 AM, Christoph Hellwig <hch@infradead.org> wrote:
> > On Wed, Sep 11, 2013 at 01:14:11AM +0800, Peng Tao wrote:
> >> The problem is access_process_vm() is not exported since certain
> >> version of kernel including the latest. According to Christoph in the
> >> other mail, access_process_vm() is also a core mm function that is not
> >> supposed to be exported. Then what kind of change shall we make in
> >> order to keep current functionality?
> >
> > You should remove the higher level functionality, kernel modules are
> > not supposed to look at userspace environment variables.
> >
> OK. I've looked at the specific case that Lustre uses
> access_process_vm() to get the jobid environment variable and package
> it into the RPC requests to server. However, it turns out that in the
> latest Lustre server code, the jobid in a request is not used
> anywhere. So it looks like we can just get rid of it.
> 
> Andreas, could you please confirm this? Is the jobid an obsolete
> parameter that can be abandoned? Or is there plan to use it somehow in
> the future?
> 
"Plan to use it in the future" is not a reason or argument to keep it today,
especially if it is something you are not supposed to do to start with.
If you ever need it, you should be able to find some other means to
support a similar functionality.

Guenter

  reply	other threads:[~2013-09-11  2: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 [this message]
2013-09-11  2:51                   ` Peng Tao
2013-09-11 16:29                     ` Christoph Hellwig
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=20130911023026.GA6273@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=andreas.dilger@intel.com \
    --cc=bergwolf@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=heiko.carstens@de.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome