From: Peter Zijlstra <peterz@infradead.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: mingo@redhat.com, mingo@kernel.org, linux-kernel@vger.kernel.org,
joe@perches.com, Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andy Lutomirski <luto@amacapital.net>,
Borislav Petkov <bp@suse.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v7] x86: Avoid pr_cont() in show_opcodes().
Date: Thu, 19 Jul 2018 16:11:20 +0200 [thread overview]
Message-ID: <20180719141120.GI2494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1532009278-5953-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp>
On Thu, Jul 19, 2018 at 11:07:58PM +0900, Tetsuo Handa wrote:
> From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
>
> Since syzbot is confused by concurrent printk() messages [1],
> this patch changes show_opcodes() to use %ph format string.
>
> When we start adding prefix to each line of printk() output,
> we will be able to handle concurrent printk() messages.
>
> [1] https://syzkaller.appspot.com/text?tag=CrashReport&x=139d342c400000
>
> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Josh Poimboeuf <jpoimboe@redhat.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Andy Lutomirski <luto@amacapital.net>
Thanks!
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2018-07-19 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 14:07 Tetsuo Handa
2018-07-19 14:11 ` Peter Zijlstra [this message]
2018-07-19 14:51 ` [tip:x86/debug] " tip-bot for Rasmus Villemoes
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=20180719141120.GI2494@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@suse.de \
--cc=joe@perches.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®