From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM/ARM64: don't enter kgdb when userspace executes a kgdb break instruction.
Date: Wed, 30 Jul 2014 12:24:14 +0100 [thread overview]
Message-ID: <20140730112414.GJ12239@arm.com> (raw)
In-Reply-To: <20140730071245.GA8954@mew.web-pass.com>
Hello,
On Wed, Jul 30, 2014 at 08:12:45AM +0100, Omar Sandoval wrote:
> The kgdb breakpoint hooks (kgdb_brk_fn and kgdb_compiled_brk_fn) should only be
> entered when a kgdb break instruction is executed from the kernel. Otherwise,
> if kgdb is enabled, a userspace program can cause the kernel to drop into the
> debugger by executing either KGDB_BREAKINST or KGDB_COMPILED_BREAK on ARM, or
> brk #KGDB_{DYN,COMPILED}_DGB_BRK_IMM on ARM64.
>
> Signed-off-by: Omar Sandoval <osandov@osandov.com>
> ---
> The following program reproduces the fixed problem on ARM:
> .globl _start
> _start:
> udf #65006 @ KGDB_BREAKINST
>
> And on ARM64:
> .globl _start
> _start:
> brk #0x400 @ KGDB_DYN_DGB_BRK_IMM
>
> arch/arm/kernel/kgdb.c | 4 ++++
> arch/arm64/include/asm/debug-monitors.h | 4 +++-
> arch/arm64/kernel/debug-monitors.c | 3 ++-
> arch/arm64/kernel/kgdb.c | 4 ++++
> 4 files changed, 13 insertions(+), 2 deletions(-)
Whilst this sounds like a worrying problem, I've failed to reproduce it
on arm64. Executing a brk instruction with either KGDB_DYN_DGB_BRK_IMM or
KDBG_COMPILED_DBG_BRK_IMM immediates from userspace results in a SIGTRAP being
delivered, assumedly because kgdb_handle_exception simply returns when kgdb
isn't active.
> diff --git a/arch/arm64/include/asm/debug-monitors.h b/arch/arm64/include/asm/debug-monitors.h
> index 6e9b5b3..e1d27ce 100644
> --- a/arch/arm64/include/asm/debug-monitors.h
> +++ b/arch/arm64/include/asm/debug-monitors.h
> @@ -105,8 +105,10 @@ void unregister_step_hook(struct step_hook *hook);
>
> struct break_hook {
> struct list_head node;
> - u32 esr_val;
> u32 esr_mask;
> + u32 esr_val;
> + u64 pstate_mask;
> + u64 pstate_val;
The following (totally untested) diff is simpler for arm64, but again, I'm
not sure we even have a problem here.
On which systems have you managed to reproduce this and how?
Will
--->8
diff --git a/arch/arm64/kernel/debug-monitors.c b/arch/arm64/kernel/debug-monitors.c
index a7fb874b595e..fe5b94078d82 100644
--- a/arch/arm64/kernel/debug-monitors.c
+++ b/arch/arm64/kernel/debug-monitors.c
@@ -315,20 +315,20 @@ static int brk_handler(unsigned long addr, unsigned int esr,
{
siginfo_t info;
- if (call_break_hook(regs, esr) == DBG_HOOK_HANDLED)
- return 0;
+ if (user_mode(regs)) {
+ info = (siginfo_t) {
+ .si_signo = SIGTRAP,
+ .si_errno = 0,
+ .si_code = TRAP_BRKPT,
+ .si_addr = (void __user *)instruction_pointer(regs),
+ };
- if (!user_mode(regs))
+ force_sig_info(SIGTRAP, &info, current);
+ } else if (call_break_hook(regs, esr) != DBG_HOOK_HANDLED) {
+ pr_warning("Unexpected kernel BRK exception at EL1\n");
return -EFAULT;
+ }
- info = (siginfo_t) {
- .si_signo = SIGTRAP,
- .si_errno = 0,
- .si_code = TRAP_BRKPT,
- .si_addr = (void __user *)instruction_pointer(regs),
- };
-
- force_sig_info(SIGTRAP, &info, current);
return 0;
}
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM/ARM64: don't enter kgdb when userspace executes a kgdb break instruction.
Date: Wed, 30 Jul 2014 12:24:14 +0100 [thread overview]
Message-ID: <20140730112414.GJ12239@arm.com> (raw)
In-Reply-To: <20140730071245.GA8954@mew.web-pass.com>
Hello,
On Wed, Jul 30, 2014 at 08:12:45AM +0100, Omar Sandoval wrote:
> The kgdb breakpoint hooks (kgdb_brk_fn and kgdb_compiled_brk_fn) should only be
> entered when a kgdb break instruction is executed from the kernel. Otherwise,
> if kgdb is enabled, a userspace program can cause the kernel to drop into the
> debugger by executing either KGDB_BREAKINST or KGDB_COMPILED_BREAK on ARM, or
> brk #KGDB_{DYN,COMPILED}_DGB_BRK_IMM on ARM64.
>
> Signed-off-by: Omar Sandoval <osandov@osandov.com>
> ---
> The following program reproduces the fixed problem on ARM:
> .globl _start
> _start:
> udf #65006 @ KGDB_BREAKINST
>
> And on ARM64:
> .globl _start
> _start:
> brk #0x400 @ KGDB_DYN_DGB_BRK_IMM
>
> arch/arm/kernel/kgdb.c | 4 ++++
> arch/arm64/include/asm/debug-monitors.h | 4 +++-
> arch/arm64/kernel/debug-monitors.c | 3 ++-
> arch/arm64/kernel/kgdb.c | 4 ++++
> 4 files changed, 13 insertions(+), 2 deletions(-)
Whilst this sounds like a worrying problem, I've failed to reproduce it
on arm64. Executing a brk instruction with either KGDB_DYN_DGB_BRK_IMM or
KDBG_COMPILED_DBG_BRK_IMM immediates from userspace results in a SIGTRAP being
delivered, assumedly because kgdb_handle_exception simply returns when kgdb
isn't active.
> diff --git a/arch/arm64/include/asm/debug-monitors.h b/arch/arm64/include/asm/debug-monitors.h
> index 6e9b5b3..e1d27ce 100644
> --- a/arch/arm64/include/asm/debug-monitors.h
> +++ b/arch/arm64/include/asm/debug-monitors.h
> @@ -105,8 +105,10 @@ void unregister_step_hook(struct step_hook *hook);
>
> struct break_hook {
> struct list_head node;
> - u32 esr_val;
> u32 esr_mask;
> + u32 esr_val;
> + u64 pstate_mask;
> + u64 pstate_val;
The following (totally untested) diff is simpler for arm64, but again, I'm
not sure we even have a problem here.
On which systems have you managed to reproduce this and how?
Will
--->8
diff --git a/arch/arm64/kernel/debug-monitors.c b/arch/arm64/kernel/debug-monitors.c
index a7fb874b595e..fe5b94078d82 100644
--- a/arch/arm64/kernel/debug-monitors.c
+++ b/arch/arm64/kernel/debug-monitors.c
@@ -315,20 +315,20 @@ static int brk_handler(unsigned long addr, unsigned int esr,
{
siginfo_t info;
- if (call_break_hook(regs, esr) == DBG_HOOK_HANDLED)
- return 0;
+ if (user_mode(regs)) {
+ info = (siginfo_t) {
+ .si_signo = SIGTRAP,
+ .si_errno = 0,
+ .si_code = TRAP_BRKPT,
+ .si_addr = (void __user *)instruction_pointer(regs),
+ };
- if (!user_mode(regs))
+ force_sig_info(SIGTRAP, &info, current);
+ } else if (call_break_hook(regs, esr) != DBG_HOOK_HANDLED) {
+ pr_warning("Unexpected kernel BRK exception at EL1\n");
return -EFAULT;
+ }
- info = (siginfo_t) {
- .si_signo = SIGTRAP,
- .si_errno = 0,
- .si_code = TRAP_BRKPT,
- .si_addr = (void __user *)instruction_pointer(regs),
- };
-
- force_sig_info(SIGTRAP, &info, current);
return 0;
}
next prev parent reply other threads:[~2014-07-30 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 7:12 [PATCH] ARM/ARM64: don't enter kgdb when userspace executes a kgdb break instruction Omar Sandoval
2014-07-30 7:12 ` Omar Sandoval
2014-07-30 7:20 ` Omar Sandoval
2014-07-30 11:24 ` Will Deacon [this message]
2014-07-30 11:24 ` Will Deacon
2014-07-31 5:33 ` Omar Sandoval
2014-07-31 5:33 ` Omar Sandoval
2014-07-31 10:46 ` Will Deacon
2014-07-31 10:46 ` Will Deacon
2014-08-01 3:07 ` Omar Sandoval
2014-08-01 3:07 ` Omar Sandoval
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=20140730112414.GJ12239@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.