mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiaoming Ni <nixiaoming@huawei.com>
To: <linux@armlinux.org.uk>, <dima@arista.com>, <will@kernel.org>,
	<jpoimboe@redhat.com>, <akpm@linux-foundation.org>,
	<christian.brauner@ubuntu.com>, <viro@zeniv.linux.org.uk>,
	<ldufour@linux.ibm.com>, <amanieu@gmail.com>, <walken@google.com>,
	<ben.dooks@codethink.co.uk>, <tglx@linutronix.de>,
	<bigeasy@linutronix.de>, <mingo@kernel.org>,
	<vincent.whitchurch@axis.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <wangle6@huawei.com>,
	<luohaizheng@huawei.com>
Subject: ping //Re: [PATCH v2] arm:traps: Don't print stack or raw PC/LR hex values in backtraces
Date: Mon, 26 Oct 2020 14:33:10 +0800	[thread overview]
Message-ID: <23a3ce81-e1b6-337f-c217-5027134c0131@huawei.com> (raw)
In-Reply-To: <20201016023141.85300-1-nixiaoming@huawei.com>

ping

On 2020/10/16 10:31, Xiaoming Ni wrote:
> Printing raw pointer values in backtraces has potential security
> implications and are of questionable value anyway.
> 
> This patch follows x86 and arm64's lead and removes the "Exception stack:"
> dump from kernel backtraces:
> 	commit a25ffd3a6302a6 ("arm64: traps: Don't print stack or raw
> 	 PC/LR values in backtraces")
> 	commit bb5e5ce545f203 ("x86/dumpstack: Remove kernel text
> 	 addresses from stack dump")
> 
> Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
> 
> -------
> v2:
>   Delete [<hex numbers>] from the stack according to the email discussion
>   in patch V1, Other information processing will be discussed in subsequent
>   patches.
> 
> v1: https://lore.kernel.org/lkml/20201009075957.110017-1-nixiaoming@huawei.com/
>    1. Don't print stack or raw PC/LR hex values in backtraces
>    2. Don't print stack mem in backtraces
>    3. if (!panic_on_oops), Don't print stack mem in __die()
> ---
>   arch/arm/kernel/process.c | 3 +--
>   arch/arm/kernel/traps.c   | 4 ++--
>   2 files changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/arm/kernel/process.c b/arch/arm/kernel/process.c
> index 8e6ace03e960..71c9e5597d39 100644
> --- a/arch/arm/kernel/process.c
> +++ b/arch/arm/kernel/process.c
> @@ -121,8 +121,7 @@ void __show_regs(struct pt_regs *regs)
>   
>   	printk("PC is at %pS\n", (void *)instruction_pointer(regs));
>   	printk("LR is at %pS\n", (void *)regs->ARM_lr);
> -	printk("pc : [<%08lx>]    lr : [<%08lx>]    psr: %08lx\n",
> -	       regs->ARM_pc, regs->ARM_lr, regs->ARM_cpsr);
> +	printk("psr: %08lx\n", regs->ARM_cpsr);
>   	printk("sp : %08lx  ip : %08lx  fp : %08lx\n",
>   	       regs->ARM_sp, regs->ARM_ip, regs->ARM_fp);
>   	printk("r10: %08lx  r9 : %08lx  r8 : %08lx\n",
> diff --git a/arch/arm/kernel/traps.c b/arch/arm/kernel/traps.c
> index 17d5a785df28..911bbf164875 100644
> --- a/arch/arm/kernel/traps.c
> +++ b/arch/arm/kernel/traps.c
> @@ -68,8 +68,8 @@ void dump_backtrace_entry(unsigned long where, unsigned long from,
>   	unsigned long end = frame + 4 + sizeof(struct pt_regs);
>   
>   #ifdef CONFIG_KALLSYMS
> -	printk("%s[<%08lx>] (%ps) from [<%08lx>] (%pS)\n",
> -		loglvl, where, (void *)where, from, (void *)from);
> +	printk("%s (%ps) from (%pS)\n",
> +		loglvl, (void *)where, (void *)from);
>   #else
>   	printk("%sFunction entered at [<%08lx>] from [<%08lx>]\n",
>   		loglvl, where, from);
> 


  reply	other threads:[~2020-10-26  6:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16  2:31 Xiaoming Ni
2020-10-26  6:33 ` Xiaoming Ni [this message]
2020-10-26 17:59   ` ping //Re: " Russell King - ARM Linux admin

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=23a3ce81-e1b6-337f-c217-5027134c0131@huawei.com \
    --to=nixiaoming@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=amanieu@gmail.com \
    --cc=ben.dooks@codethink.co.uk \
    --cc=bigeasy@linutronix.de \
    --cc=christian.brauner@ubuntu.com \
    --cc=dima@arista.com \
    --cc=jpoimboe@redhat.com \
    --cc=ldufour@linux.ibm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luohaizheng@huawei.com \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.whitchurch@axis.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=walken@google.com \
    --cc=wangle6@huawei.com \
    --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

all inboxes | Powered by JetHome®