From: Andrew Morton <akpm@linux-foundation.org>
To: Helge Deller <deller@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
Michael Kerrisk <mtk.manpages@googlemail.com>,
linux-api@vger.kernel.org
Subject: Re: [PATCH] prctl: implement PR_GET_ENDIAN for all architectures
Date: Wed, 1 Feb 2017 14:03:22 -0800 [thread overview]
Message-ID: <20170201140322.b469641861861caf8cf6da48@linux-foundation.org> (raw)
In-Reply-To: <7c60f97a-4b63-5eff-e837-186f9a31c5a2@gmx.de>
On Wed, 1 Feb 2017 20:47:06 +0100 Helge Deller <deller@gmx.de> wrote:
> Hi Andrew,
>
> On 01.02.2017 01:26, Andrew Morton wrote:
> > On Sat, 28 Jan 2017 12:13:10 +0100 Helge Deller <deller@gmx.de> wrote:
> >
> >> The prctl(PR_GET_ENDIAN) syscall was added to Kernel 2.6.18, but
> >> implemented for PowerPC only.
> >> This trivial patch adds support for this syscall for all other architectures.
> >
> > Seems reasonable. I guess.
>
> Heck, I did forgot but I submitted a similar patch 8 years ago:
> http://www.serverphorums.com/read.php?12,51902
>
> > Why is this needed?
>
> It's not actually needed beside the trivial reason of providing an interface
> not just for one single architecture.
>
> After reading the discussion from 2009 again, I'm fine if
> you would simply drop the patch. The decision up to you.
Can't decide. I guess that moving it into the kernel will, over time,
eliminate some irritating ifdefs from userspace code.
The implementation itself is a bit half-assed. The put_user() in
arch/powerpc/kernel/process.c:get_endian() should be moved into
kernel/sys.c. So the arch code only does the "what endianness am I"
function and common code copies that out to userspace.
next prev parent reply other threads:[~2017-02-01 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 11:13 Helge Deller
2017-02-01 0:26 ` Andrew Morton
2017-02-01 19:47 ` Helge Deller
2017-02-01 22:03 ` Andrew Morton [this message]
2017-02-01 23:12 ` James Bottomley
2017-02-02 5:08 ` Andy Lutomirski
2017-02-05 11:48 ` Matt Turner
2017-02-05 13:15 ` Maciej W. Rozycki
2017-02-15 5:20 ` Michael Ellerman
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=20170201140322.b469641861861caf8cf6da48@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=deller@gmx.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mtk.manpages@googlemail.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
all inboxes | Powered by JetHome®