From: Jason Wessel <jason.wessel@windriver.com>
To: Dongdong Deng <dongdong.deng@windriver.com>
Cc: kgdb-bugreport@lists.sourceforge.net, "Hai,
Shan" <shan.hai@windriver.com>,
linuxppc-dev@lists.ozlabs.org,
Sergei Shtylyov <sshtylyov@mvista.com>,
miltonm@bga.com
Subject: Re: [PATCH] kgdb, ppc: Corrected the address using of current->thread.evr register
Date: Tue, 16 Nov 2010 16:02:02 -0600 [thread overview]
Message-ID: <4CE2FF5A.402@windriver.com> (raw)
In-Reply-To: <1289912316-4580-1-git-send-email-dongdong.deng@windriver.com>
On 11/16/2010 06:58 AM, Dongdong Deng wrote:
> Passing the address of current->thread.evr register to memcpy function.
>
>
It turns out that out of all of my test configs and targets I did not
have any that defined both CONFIG_FSL_BOOKE and CONFIG_SPE else this
would have been caught in testing because will definitely crash
dereferencing the contents of the evr registers.
> Signed-off-by: Dongdong Deng <dongdong.deng@windriver.com>
> CC: Hai Shan <shan.hai@windriver.com>
> CC: Milton Miller <miltonm@bga.com>
> CC: linuxppc-dev@lists.ozlabs.org
> ---
> arch/powerpc/kernel/kgdb.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/kernel/kgdb.c b/arch/powerpc/kernel/kgdb.c
> index 7a9db64..781acff 100644
> --- a/arch/powerpc/kernel/kgdb.c
> +++ b/arch/powerpc/kernel/kgdb.c
> @@ -337,7 +337,7 @@ char *dbg_get_reg(int regno, void *mem, struct pt_regs *regs)
> /* FP registers 32 -> 63 */
> #if defined(CONFIG_FSL_BOOKE) && defined(CONFIG_SPE)
> if (current)
> - memcpy(mem, current->thread.evr[regno-32],
> + memcpy(mem, (void *)¤t->thread.evr[regno-32],
> dbg_reg_def[regno].size);
>
As Sergei already pointed out, the (void *) casts should not be needed here.
This would have been fixed correctly had I seen the compile warnings
from the CONFIG_SPE at the test phase. Namely at the compile phase
doesn't even complete:
arch/powerpc/kernel/kgdb.c: In function 'dbg_get_reg':
arch/powerpc/kernel/kgdb.c:341: error: passing argument 2 of 'memcpy'
makes pointer from integer without a cast
arch/powerpc/include/asm/string.h:25: note: expected 'const void *' but
argument is of type 'long unsigned int'
arch/powerpc/kernel/kgdb.c: In function 'dbg_set_reg':
arch/powerpc/kernel/kgdb.c:366: error: passing argument 1 of 'memcpy'
makes pointer from integer without a cast
arch/powerpc/include/asm/string.h:25: note: expected 'void *' but
argument is of type 'long unsigned int'
Moral of the story... I now have a board and config with the SPE turned
on, and after boot testing confirmed the evr registers are working.
I plan to have a pull request out to Linus with this fix and several
other accumulated regression fixes sometime in the next 48 hours.
Thanks,
Jason.
next prev parent reply other threads:[~2010-11-16 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 12:58 [PATCH] kgdb, ppc: Corrected the address using of current->thread.evr register Dongdong Deng
2010-11-16 13:02 ` [Kgdb-bugreport] " Sergei Shtylyov
2010-11-16 22:02 ` Jason Wessel [this message]
2010-11-17 17:16 ` Kumar Gala
2010-11-17 17:21 ` Jason Wessel
2010-11-17 17:52 ` Kumar Gala
2010-11-17 18:58 ` Kumar Gala
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=4CE2FF5A.402@windriver.com \
--to=jason.wessel@windriver.com \
--cc=dongdong.deng@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=miltonm@bga.com \
--cc=shan.hai@windriver.com \
--cc=sshtylyov@mvista.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;
as well as URLs for NNTP newsgroup(s).