From: "tiejun.chen" <tiejun.chen@windriver.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
jason.wessel@windriver.com
Subject: Re: [v2][PATCH 3/3] powerpc/kgdb: restore current_thread_info properly
Date: Thu, 23 Aug 2012 11:24:54 +0800 [thread overview]
Message-ID: <5035A286.3090508@windriver.com> (raw)
In-Reply-To: <1345691650.10190.31.camel@haakon2.linux-iscsi.org>
On 08/23/2012 11:14 AM, Nicholas A. Bellinger wrote:
> On Thu, 2012-08-23 at 10:10 +0800, Tiejun Chen wrote:
>> For powerpc BooKE and e200, singlestep is handled on the critical/dbg
>> exception stack. This causes current_thread_info() to fail for kgdb
>> internal, so previously We work around this issue by copying
>> the thread_info from the kernel stack before calling kgdb_handle_exception,
>> and copying it back afterwards.
>>
>> But actually we don't do this properly. We should backup current_thread_info
>> then restore that when exit.
>>
>> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
>> ---
>> v2: fix a typo in patch head description.
>>
>> arch/powerpc/kernel/kgdb.c | 11 +++++++++--
>> 1 files changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/kgdb.c b/arch/powerpc/kernel/kgdb.c
>> index 05adb69..c470a40 100644
>> --- a/arch/powerpc/kernel/kgdb.c
>> +++ b/arch/powerpc/kernel/kgdb.c
>> @@ -25,6 +25,7 @@
>> #include <asm/processor.h>
>> #include <asm/machdep.h>
>> #include <asm/debug.h>
>> +#include <linux/slab.h>
>>
>> /*
>> * This table contains the mapping between PowerPC hardware trap types, and
>> @@ -153,6 +154,8 @@ static int kgdb_handle_breakpoint(struct pt_regs *regs)
>> static int kgdb_singlestep(struct pt_regs *regs)
>> {
>> struct thread_info *thread_info, *exception_thread_info;
>> + struct thread_info *backup_current_thread_info = \
>> + (struct thread_info *)kmalloc(sizeof(struct thread_info), GFP_KERNEL);
>>
>
> Looks like a rouge '\' in the above assignment..
Remove that :)
Thanks
Tiejun
WARNING: multiple messages have this Message-ID (diff)
From: "tiejun.chen" <tiejun.chen@windriver.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: <benh@kernel.crashing.org>, <jason.wessel@windriver.com>,
<linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [v2][PATCH 3/3] powerpc/kgdb: restore current_thread_info properly
Date: Thu, 23 Aug 2012 11:24:54 +0800 [thread overview]
Message-ID: <5035A286.3090508@windriver.com> (raw)
In-Reply-To: <1345691650.10190.31.camel@haakon2.linux-iscsi.org>
On 08/23/2012 11:14 AM, Nicholas A. Bellinger wrote:
> On Thu, 2012-08-23 at 10:10 +0800, Tiejun Chen wrote:
>> For powerpc BooKE and e200, singlestep is handled on the critical/dbg
>> exception stack. This causes current_thread_info() to fail for kgdb
>> internal, so previously We work around this issue by copying
>> the thread_info from the kernel stack before calling kgdb_handle_exception,
>> and copying it back afterwards.
>>
>> But actually we don't do this properly. We should backup current_thread_info
>> then restore that when exit.
>>
>> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
>> ---
>> v2: fix a typo in patch head description.
>>
>> arch/powerpc/kernel/kgdb.c | 11 +++++++++--
>> 1 files changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/kgdb.c b/arch/powerpc/kernel/kgdb.c
>> index 05adb69..c470a40 100644
>> --- a/arch/powerpc/kernel/kgdb.c
>> +++ b/arch/powerpc/kernel/kgdb.c
>> @@ -25,6 +25,7 @@
>> #include <asm/processor.h>
>> #include <asm/machdep.h>
>> #include <asm/debug.h>
>> +#include <linux/slab.h>
>>
>> /*
>> * This table contains the mapping between PowerPC hardware trap types, and
>> @@ -153,6 +154,8 @@ static int kgdb_handle_breakpoint(struct pt_regs *regs)
>> static int kgdb_singlestep(struct pt_regs *regs)
>> {
>> struct thread_info *thread_info, *exception_thread_info;
>> + struct thread_info *backup_current_thread_info = \
>> + (struct thread_info *)kmalloc(sizeof(struct thread_info), GFP_KERNEL);
>>
>
> Looks like a rouge '\' in the above assignment..
Remove that :)
Thanks
Tiejun
next prev parent reply other threads:[~2012-08-23 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 2:10 [v2][PATCH 1/3] kgdb,ppc: do not set kgdb_single_step on ppc Tiejun Chen
2012-08-23 2:10 ` Tiejun Chen
2012-08-23 2:10 ` [v2][PATCH 2/3] powerpc: Bail out of KGDB when we've been triggered Tiejun Chen
2012-08-23 2:10 ` Tiejun Chen
2012-08-23 2:10 ` [v2][PATCH 3/3] powerpc/kgdb: restore current_thread_info properly Tiejun Chen
2012-08-23 2:10 ` Tiejun Chen
2012-08-23 3:14 ` Nicholas A. Bellinger
2012-08-23 3:14 ` Nicholas A. Bellinger
2012-08-23 3:24 ` tiejun.chen [this message]
2012-08-23 3:24 ` tiejun.chen
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=5035A286.3090508@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nab@linux-iscsi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.