From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org, anton@samba.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] powerpc/le: fix endianness of the arguments passed to the ppc_rtas() syscall
Date: Wed, 05 Mar 2014 18:20:06 +0100 [thread overview]
Message-ID: <20140305172006.26117.57219.stgit@bahia.local> (raw)
RTAS manipulates its input and output arguments in big endian order.
I have looked at factoring some lines with rtas_call() but it is not really
worth it because of the variable arguments.
Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
---
arch/powerpc/kernel/rtas.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/rtas.c b/arch/powerpc/kernel/rtas.c
index 4cf674d..00dbe36 100644
--- a/arch/powerpc/kernel/rtas.c
+++ b/arch/powerpc/kernel/rtas.c
@@ -1020,6 +1020,7 @@ asmlinkage int ppc_rtas(struct rtas_args __user *uargs)
char *buff_copy, *errbuf = NULL;
int nargs;
int rc;
+ int i;
if (!capable(CAP_SYS_ADMIN))
return -EPERM;
@@ -1056,9 +1057,19 @@ asmlinkage int ppc_rtas(struct rtas_args __user *uargs)
flags = lock_rtas();
- rtas.args = args;
+ rtas.args.token = cpu_to_be32(args.token);
+ rtas.args.nargs = cpu_to_be32(args.nargs);
+ rtas.args.nret = cpu_to_be32(args.nret);
+ for (i = 0; i < nargs; ++i)
+ rtas.args.args[i] = cpu_to_be32(args.args[i]);
+ rtas.args.rets = &rtas.args.args[nargs];
+ for (i = 0; i < args.nret; ++i)
+ rtas.args.rets[i] = 0;
+
enter_rtas(__pa(&rtas.args));
- args = rtas.args;
+
+ for (i = 0; i < args.nret; ++i)
+ args.rets[i] = be32_to_cpu(rtas.args.rets[i]);
/* A -1 return code indicates that the last command couldn't
be completed due to a hardware error. */
next reply other threads:[~2014-03-05 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 17:20 Greg Kurz [this message]
2014-03-06 5:43 ` [PATCH] powerpc/le: fix endianness of the arguments passed to the ppc_rtas() syscall Benjamin Herrenschmidt
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=20140305172006.26117.57219.stgit@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).