[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180427065817.tedhin5sy7brgq7m@gmail.com>
Date: Fri, 27 Apr 2018 08:58:17 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
Ingo Molnar <mingo@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
"David S . Miller" <davem@...emloft.net>,
Jon Medhurst <tixy@...aro.org>,
Will Deacon <will.deacon@....com>,
Arnd Bergmann <arnd@...db.de>,
David Howells <dhowells@...hat.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
"Tobin C . Harding" <me@...in.cc>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Richter <tmricht@...ux.ibm.com>,
akpm@...ux-foundation.org, acme@...nel.org, rostedt@...dmis.org,
brueckner@...ux.vnet.ibm.com, schwidefsky@...ibm.com,
stable@...r.kernel.org
Subject: Re: [PATCH v3 5/7] kprobes/x86: Fix %p uses in error messages
* Masami Hiramatsu <mhiramat@...nel.org> wrote:
> (addr < (u8 *) jprobe_return_end)) {
> if (stack_addr(regs) != saved_sp) {
> struct pt_regs *saved_regs = &kcb->jprobe_saved_regs;
> - printk(KERN_ERR
> - "current sp %p does not match saved sp %p\n",
> + pr_err("current sp %pS does not match saved sp %pS\n",
> stack_addr(regs), saved_sp);
Why does this use %pS? Stack pointers are typically pointing into general kernel
RAM, which is totally pointless to display 'symbolically'.
Thanks,
Ingo
Powered by blists - more mailing lists