| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 17 Jul 2020 15:39:51 -0700
From: Doug Anderson <dianders@...omium.org>
To: Daniel Thompson <daniel.thompson@...aro.org>
Cc: Jason Wessel <jason.wessel@...driver.com>,
Peter Zijlstra <peterz@...radead.org>,
Sumit Garg <sumit.garg@...aro.org>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Will Deacon <will@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
kgdb-bugreport@...ts.sourceforge.net,
LKML <linux-kernel@...r.kernel.org>,
Patch Tracking <patches@...aro.org>
Subject: Re: [PATCH v2 2/3] kgdb: Use the kprobe blocklist to limit single stepping
Hi,
On Thu, Jul 16, 2020 at 8:20 AM Daniel Thompson
<daniel.thompson@...aro.org> wrote:
>
> If we are running in a part of the kernel that dislikes breakpoint
> debugging then it is very unlikely to be safe to single step. Add
> some safety rails to prevent stepping through anything on the kprobe
> blocklist.
>
> As part of this kdb_ss() will no longer set the DOING_SS flags when it
> requests a step. This is safe because this flag is already redundant,
> returning KDB_CMD_SS is all that is needed to request a step (and this
> saves us from having to unset the flag if the safety check fails).
>
> Signed-off-by: Daniel Thompson <daniel.thompson@...aro.org>
> ---
> include/linux/kgdb.h | 1 +
> kernel/debug/debug_core.c | 13 +++++++++++++
> kernel/debug/gdbstub.c | 10 +++++++++-
> kernel/debug/kdb/kdb_bp.c | 8 ++------
> kernel/debug/kdb/kdb_main.c | 10 ++++++++--
> 5 files changed, 33 insertions(+), 9 deletions(-)
>
> diff --git a/include/linux/kgdb.h b/include/linux/kgdb.h
> index 7caba4604edc..aefe823998cb 100644
> --- a/include/linux/kgdb.h
> +++ b/include/linux/kgdb.h
> @@ -214,6 +214,7 @@ extern void kgdb_arch_set_pc(struct pt_regs *regs, unsigned long pc);
>
> /* Optional functions. */
> extern int kgdb_validate_break_address(unsigned long addr);
> +extern int kgdb_validate_single_step_address(unsigned long addr);
> extern int kgdb_arch_set_breakpoint(struct kgdb_bkpt *bpt);
> extern int kgdb_arch_remove_breakpoint(struct kgdb_bkpt *bpt);
>
> diff --git a/kernel/debug/debug_core.c b/kernel/debug/debug_core.c
> index 133a361578dc..4b59bcc90c5d 100644
> --- a/kernel/debug/debug_core.c
> +++ b/kernel/debug/debug_core.c
> @@ -208,6 +208,19 @@ int __weak kgdb_validate_break_address(unsigned long addr)
> return err;
> }
>
> +int __weak kgdb_validate_single_step_address(unsigned long addr)
> +{
> + /*
> + * Disallow stepping when we are executing code that is marked
> + * as unsuitable for breakpointing... stepping won't be safe
> + * either!
> + */
> + if (kgdb_within_blocklist(addr))
> + return -EINVAL;
> +
> + return 0;
> +}
> +
> unsigned long __weak kgdb_arch_pc(int exception, struct pt_regs *regs)
> {
> return instruction_pointer(regs);
> diff --git a/kernel/debug/gdbstub.c b/kernel/debug/gdbstub.c
> index 61774aec46b4..f1c88007cc2b 100644
> --- a/kernel/debug/gdbstub.c
> +++ b/kernel/debug/gdbstub.c
> @@ -1041,8 +1041,16 @@ int gdb_serial_stub(struct kgdb_state *ks)
> if (tmp == 0)
> break;
> /* Fall through - on tmp < 0 */
> - case 'c': /* Continue packet */
> case 's': /* Single step packet */
> + error = kgdb_validate_single_step_address(
> + kgdb_arch_pc(ks->ex_vector,
> + ks->linux_regs));
I'm a little confused. Isn't this like saying "if
(i_am_standing_in_acid) dont_step_into_acid"?
Specifically you're checking the _current_ PC to see if it's in the
blocklist, right? ...but you've already (effectively) dropped into
the debugger at that location, so if it really was a problem wouldn't
we already be in trouble?
What you really want (I think?) is to know if the instruction that
you're stepping into is in the blocklist, right? ...but you can't
know that because it requires a full instruction emulator (that's why
CPUs have "single step mode").
I guess you get a marginal benefit if someone manually set their
instruction pointer to be an address in the middle of a blocklisted
function and then trying to step, but I'm not sure that's really
something we need to add code for?
It feels like the right solution is that the architecture-specific
single-step code should simply consider a single-step through a
blocklisted area to be a step through one giant instruction.
> + if (error != 0) {
> + error_packet(remcom_out_buffer, error);
> + break;
> + }
> + fallthrough;
> + case 'c': /* Continue packet */
> if (kgdb_contthread && kgdb_contthread != current) {
> /* Can't switch threads in kgdb */
> error_packet(remcom_out_buffer, -EINVAL);
> diff --git a/kernel/debug/kdb/kdb_bp.c b/kernel/debug/kdb/kdb_bp.c
> index ec4940146612..4853c413f579 100644
> --- a/kernel/debug/kdb/kdb_bp.c
> +++ b/kernel/debug/kdb/kdb_bp.c
> @@ -507,18 +507,14 @@ static int kdb_bc(int argc, const char **argv)
> * None.
> * Remarks:
> *
> - * Set the arch specific option to trigger a debug trap after the next
> - * instruction.
> + * KDB_CMD_SS is a command that our caller acts on to effect the step.
> */
>
> static int kdb_ss(int argc, const char **argv)
> {
> if (argc != 0)
> return KDB_ARGCOUNT;
> - /*
> - * Set trace flag and go.
> - */
> - KDB_STATE_SET(DOING_SS);
> +
> return KDB_CMD_SS;
> }
>
> diff --git a/kernel/debug/kdb/kdb_main.c b/kernel/debug/kdb/kdb_main.c
> index 5c7949061671..cd40bf780b93 100644
> --- a/kernel/debug/kdb/kdb_main.c
> +++ b/kernel/debug/kdb/kdb_main.c
> @@ -1189,7 +1189,7 @@ static int kdb_local(kdb_reason_t reason, int error, struct pt_regs *regs,
> kdb_dbtrap_t db_result)
> {
> char *cmdbuf;
> - int diag;
> + int diag, res;
> struct task_struct *kdb_current =
> kdb_curr_task(raw_smp_processor_id());
>
> @@ -1346,10 +1346,16 @@ static int kdb_local(kdb_reason_t reason, int error, struct pt_regs *regs,
> }
> if (diag == KDB_CMD_GO
> || diag == KDB_CMD_CPU
> - || diag == KDB_CMD_SS
> || diag == KDB_CMD_KGDB)
> break;
>
> + if (diag == KDB_CMD_SS) {
> + res = kgdb_validate_single_step_address(instruction_pointer(regs));
Is it legit to use instruction_pointer() directly? Should you be
calling kgdb_arch_pc() ...or does that just account for having just
hit a breakpoint?
Powered by blists - more mailing lists