mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: linas@austin.ibm.com
To: paulus@au1.ibm.com, paulus@samba.org
Cc: linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: [PATCH] PPC64: Janitor log_rtas_error() call arguments
Date: Tue, 29 Jun 2004 16:41:01 -0500	[thread overview]
Message-ID: <20040629164100.O21634@forte.austin.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]



Paul,

Please apply the following patch to the ameslab tree and/or forward to
the official 2.6 tree maintainers, as appropriate.  This patch fixes the 
confusing argument aliasing of the log_rtas_error() subroutine.  

This patch makes no functional changes, it just cleans up some 
strange usage.

The rtas_args used to communicate with firmware are always taken
from the paca struct, so as to keep the args at a fixed, low-memory 
location.  But the log_rtas_error() routine also took an rtas_args
pointer, which it assumed was aliased to the paca struct.  This
aliasing is both un-neccessary, and confusing; this patch eliminates
this confusion.

Signed-off-by: Linas Vepstas <linas@linas.org>

--linas

[-- Attachment #2: rtas-args-aliasing.patch --]
[-- Type: text/plain, Size: 1807 bytes --]

--- arch/ppc64/kernel/rtas.c.orig	2004-06-29 16:01:47.000000000 -0500
+++ arch/ppc64/kernel/rtas.c	2004-06-29 16:16:08.000000000 -0500
@@ -99,9 +99,9 @@ rtas_token(const char *service)
 
 
 static int
-__log_rtas_error(struct rtas_args *rtas_args)
+__log_rtas_error(void)
 {
-	struct rtas_args err_args, temp_args;
+	struct rtas_args err_args, save_args;
 
 	err_args.token = rtas_token("rtas-last-error");
 	err_args.nargs = 2;
@@ -112,7 +112,7 @@ __log_rtas_error(struct rtas_args *rtas_
 	err_args.args[1] = RTAS_ERROR_LOG_MAX;
 	err_args.args[2] = 0;
 
-	temp_args = *rtas_args;
+	save_args = get_paca()->xRtas;
 	get_paca()->xRtas = err_args;
 
 	PPCDBG(PPCDBG_RTAS, "\tentering rtas with 0x%lx\n",
@@ -121,19 +121,19 @@ __log_rtas_error(struct rtas_args *rtas_
 	PPCDBG(PPCDBG_RTAS, "\treturned from rtas ...\n");
 
 	err_args = get_paca()->xRtas;
-	get_paca()->xRtas = temp_args;
+	get_paca()->xRtas = save_args;
 
 	return err_args.rets[0];
 }
 
 void
-log_rtas_error(struct rtas_args	*rtas_args)
+log_rtas_error(void)
 {
 	unsigned long s;
 	int rc;
 
 	spin_lock_irqsave(&rtas.lock, s);
-	rc = __log_rtas_error(rtas_args);
+	rc = __log_rtas_error();
 	spin_unlock_irqrestore(&rtas.lock, s);
 	if (rc == 0)
 		log_error(rtas_err_buf, ERR_TYPE_RTAS_LOG, 0);
@@ -181,7 +181,7 @@ rtas_call(int token, int nargs, int nret
 	PPCDBG(PPCDBG_RTAS, "\treturned from rtas ...\n");
 
 	if (rtas_args->rets[0] == -1)
-		logit = (__log_rtas_error(rtas_args) == 0);
+		logit = (__log_rtas_error() == 0);
 
 	ifppcdebug(PPCDBG_RTAS) {
 		for(i=0; i < nret ;i++)
@@ -489,7 +489,7 @@ asmlinkage int ppc_rtas(struct rtas_args
 
 	args.rets  = (rtas_arg_t *)&(args.args[nargs]);
 	if (args.rets[0] == -1)
-		log_rtas_error(&args);
+		log_rtas_error();
 
 	/* Copy out args. */
 	if (copy_to_user(uargs->args + nargs,

             reply	other threads:[~2004-06-30  3:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 21:41 linas [this message]
2004-06-30 12:11 Paul Mackerras

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=20040629164100.O21634@forte.austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@lists.linuxppc.org \
    --cc=paulus@au1.ibm.com \
    --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

all inboxes | Powered by JetHome®