From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH, resend 1/1] x86/kernel: re-use %*ph specifier
Date: Sun, 11 Oct 2015 22:20:49 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1510112215550.6097@nanos> (raw)
In-Reply-To: <1443791813-142403-1-git-send-email-andriy.shevchenko@linux.intel.com>
On Fri, 2 Oct 2015, Andy Shevchenko wrote:
> %*ph specifier allows to dump data in hex format using the poiter to a buffer.
> This is suitable to use here.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> arch/x86/kernel/jump_label.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/jump_label.c b/arch/x86/kernel/jump_label.c
> index e565e0e..8da5254 100644
> --- a/arch/x86/kernel/jump_label.c
> +++ b/arch/x86/kernel/jump_label.c
> @@ -31,8 +31,8 @@ static void bug_at(unsigned char *ip, int line)
> * Something went wrong. Crash the box, as something could be
> * corrupting the kernel.
> */
> - pr_warning("Unexpected op at %pS [%p] (%02x %02x %02x %02x %02x) %s:%d\n",
> - ip, ip, ip[0], ip[1], ip[2], ip[3], ip[4], __FILE__, line);
> + pr_warn("Unexpected op at %pS [%p] (%5ph) %s:%d\n",
> + ip, ip, ip, __FILE__, line);
We really do not need the file printed here. We better have the
message starting with "jumplabel: Unexpected ...." And it should not
be a warning as we BUG() right after that. pr_crit() is probably the
right choice, though I wonder whether we should panic() right away
when that happens.
> BUG();
Thanks,
tglx
prev parent reply other threads:[~2015-10-11 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 13:16 Andy Shevchenko
2015-10-11 20:20 ` Thomas Gleixner [this message]
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=alpine.DEB.2.11.1510112215550.6097@nanos \
--to=tglx@linutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=x86@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®