From: Masami Hiramatsu <mhiramat@kernel.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
Douglas Anderson <dianders@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
sumit.garg@linaro.org, pmladek@suse.com,
sergey.senozhatsky@gmail.com, will@kernel.org,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org, patches@linaro.org
Subject: Re: [RFC PATCH 3/4] kgdb: Add NOKPROBE labels on the trap handler functions
Date: Thu, 11 Jun 2020 21:43:14 +0900 [thread overview]
Message-ID: <20200611214314.bc3ab1fb7000cf50eb037a6f@kernel.org> (raw)
In-Reply-To: <20200605132130.1411255-4-daniel.thompson@linaro.org>
On Fri, 5 Jun 2020 14:21:29 +0100
Daniel Thompson <daniel.thompson@linaro.org> wrote:
> Currently kgdb honours the kprobe blacklist but doesn't place its own
> trap handling code on the list. Add macros to discourage attempting to
> use kgdb to debug itself.
>
> These changes do not make it impossible to provoke recursive trapping
> since they do not cover all the calls that can be made on kgdb's entry
> logic. However going much further whilst we are sharing the kprobe
> blacklist risks reducing the capabilities of kprobe and this is a bad
> trade off (especially so given kgdb's users are currently conditioned to
> avoid recursive traps).
>
> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
> ---
> kernel/debug/debug_core.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/debug/debug_core.c b/kernel/debug/debug_core.c
> index 4a2df4509fe1..21d1d91da4bb 100644
> --- a/kernel/debug/debug_core.c
> +++ b/kernel/debug/debug_core.c
> @@ -184,6 +184,7 @@ int __weak kgdb_arch_remove_breakpoint(struct kgdb_bkpt *bpt)
> return probe_kernel_write((char *)bpt->bpt_addr,
> (char *)bpt->saved_instr, BREAK_INSTR_SIZE);
> }
> +NOKPROBE_SYMBOL(kgdb_arch_remove_breakpoint);
>
> int __weak kgdb_validate_break_address(unsigned long addr)
> {
> @@ -321,6 +322,7 @@ static void kgdb_flush_swbreak_addr(unsigned long addr)
> /* Force flush instruction cache if it was outside the mm */
> flush_icache_range(addr, addr + BREAK_INSTR_SIZE);
> }
> +NOKPROBE_SYMBOL(kgdb_flush_swbreak_addr);
>
> /*
> * SW breakpoint management:
> @@ -411,6 +413,7 @@ int dbg_deactivate_sw_breakpoints(void)
> }
> return ret;
> }
> +NOKPROBE_SYMBOL(dbg_deactivate_sw_breakpoints);
>
> int dbg_remove_sw_break(unsigned long addr)
> {
> @@ -567,6 +570,7 @@ static int kgdb_reenter_check(struct kgdb_state *ks)
>
> return 1;
> }
> +NOKPROBE_SYMBOL(kgdb_reenter_check);
>
> static void dbg_touch_watchdogs(void)
> {
> @@ -801,6 +805,7 @@ static int kgdb_cpu_enter(struct kgdb_state *ks, struct pt_regs *regs,
>
> return kgdb_info[cpu].ret_state;
> }
> +NOKPROBE_SYMBOL(kgdb_cpu_enter);
>
> /*
> * kgdb_handle_exception() - main entry point from a kernel exception
> @@ -845,6 +850,7 @@ kgdb_handle_exception(int evector, int signo, int ecode, struct pt_regs *regs)
> arch_kgdb_ops.enable_nmi(1);
> return ret;
> }
> +NOKPROBE_SYMBOL(kgdb_handle_exception);
>
> /*
> * GDB places a breakpoint at this function to know dynamically loaded objects.
> @@ -879,6 +885,7 @@ int kgdb_nmicallback(int cpu, void *regs)
> #endif
> return 1;
> }
> +NOKPROBE_SYMBOL(kgdb_nmicallback);
>
> int kgdb_nmicallin(int cpu, int trapnr, void *regs, int err_code,
> atomic_t *send_ready)
> @@ -904,6 +911,7 @@ int kgdb_nmicallin(int cpu, int trapnr, void *regs, int err_code,
> #endif
> return 1;
> }
> +NOKPROBE_SYMBOL(kgdb_nmicallin);
>
> static void kgdb_console_write(struct console *co, const char *s,
> unsigned count)
> @@ -1204,7 +1212,6 @@ noinline void kgdb_breakpoint(void)
> atomic_dec(&kgdb_setting_breakpoint);
> }
> EXPORT_SYMBOL_GPL(kgdb_breakpoint);
> -NOKPROBE_SYMBOL(kgdb_breakpoint);
BTW, why did you mark this NOKPROBE in 2/4 and remove it 3/4 again?
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-06-11 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 13:21 [RFC PATCH 0/4] kgdb: Honour the kprobe blacklist when setting breakpoints Daniel Thompson
2020-06-05 13:21 ` [RFC PATCH 1/4] " Daniel Thompson
2020-06-05 13:21 ` [RFC PATCH 2/4] kgdb: Use the kprobe blacklist to limit single stepping Daniel Thompson
2020-06-05 13:21 ` [RFC PATCH 3/4] kgdb: Add NOKPROBE labels on the trap handler functions Daniel Thompson
2020-06-11 12:43 ` Masami Hiramatsu [this message]
2020-06-05 13:21 ` [RFC PATCH 4/4] kprobes: Allow the kprobes blacklist to be compiled independently Daniel Thompson
2020-06-05 14:29 ` [RFC PATCH 0/4] kgdb: Honour the kprobe blacklist when setting breakpoints Peter Zijlstra
2020-06-05 14:44 ` Peter Zijlstra
2020-06-08 13:50 ` Daniel Thompson
2020-06-08 12:43 ` Daniel Thompson
2020-06-11 12:42 ` Masami Hiramatsu
2020-06-11 14:32 ` Daniel Thompson
2020-06-12 10:13 ` Masami Hiramatsu
2020-06-12 11:04 ` Daniel Thompson
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=20200611214314.bc3ab1fb7000cf50eb037a6f@kernel.org \
--to=mhiramat@kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sumit.garg@linaro.org \
--cc=will@kernel.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