From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: perf: perf_fuzzer quickly locks up on 4.15-rc7
Date: Tue, 9 Jan 2018 17:20:19 +0100 [thread overview]
Message-ID: <20180109162019.GL3040@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180109161606.etvacvfe6rq777ps@gmail.com>
On Tue, Jan 09, 2018 at 05:16:06PM +0100, Ingo Molnar wrote:
> > + force_early_printk
> > + Forcefully uses early_console (as per earlyprintk=)
> > + usage for regular printk, bypassing everything,
> > + including the syslog (dmesg will be empty).
>
> BTW., this looks very useful - please consider pushing it upstream if it does not
> hurt any of the other syslog usecases.
I've posted it a number of times, the printk people didn't hate it but
haven't merged it either. Instead they continue working on making it a
bigger trainwreck...
I'll post it again later when we're not chasing spectres and meltdowns.
next prev parent reply other threads:[~2018-01-09 16:20 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 16:12 perf: perf_fuzzer quickly locks up on 4.15-rc7 Vince Weaver
2018-01-08 17:30 ` Ingo Molnar
2018-01-08 20:29 ` Vince Weaver
2018-01-09 10:25 ` Peter Zijlstra
2018-01-09 13:26 ` Peter Zijlstra
2018-01-09 13:36 ` Peter Zijlstra
2018-01-09 13:44 ` Vince Weaver
2018-01-09 15:12 ` Peter Zijlstra
2018-01-09 15:24 ` Vince Weaver
2018-01-09 15:33 ` Peter Zijlstra
2018-01-09 15:56 ` Vince Weaver
2018-01-09 16:05 ` Peter Zijlstra
2018-01-09 17:07 ` Josh Poimboeuf
2018-01-11 5:25 ` Josh Poimboeuf
2018-01-11 19:00 ` Vince Weaver
2018-01-11 19:21 ` Josh Poimboeuf
2018-01-11 19:50 ` Peter Zijlstra
2018-01-11 19:57 ` Vince Weaver
2018-01-11 20:43 ` Vince Weaver
2018-05-01 13:29 ` perf: fuzzer causes stack going in wrong direction warnings Vince Weaver
2018-05-01 13:58 ` Josh Poimboeuf
2018-05-01 19:59 ` Vince Weaver
2018-05-01 22:04 ` Josh Poimboeuf
2018-05-02 20:50 ` Josh Poimboeuf
2018-05-04 14:35 ` Vince Weaver
2018-05-04 16:25 ` Josh Poimboeuf
2018-05-04 17:00 ` Vince Weaver
2018-05-05 15:38 ` Vince Weaver
2018-05-05 18:29 ` Josh Poimboeuf
2018-05-06 23:49 ` Josh Poimboeuf
2018-05-10 13:48 ` Peter Zijlstra
2018-05-10 14:27 ` Josh Poimboeuf
2018-05-10 23:16 ` Josh Poimboeuf
2018-01-09 16:16 ` perf: perf_fuzzer quickly locks up on 4.15-rc7 Ingo Molnar
2018-01-09 16:20 ` Peter Zijlstra [this message]
2018-01-09 17:18 ` Vince Weaver
2018-01-10 15:28 ` Vince Weaver
2018-01-09 16:14 ` Peter Zijlstra
2018-01-09 17:53 ` Steven Rostedt
2018-01-09 18:02 ` Peter Zijlstra
2018-01-09 18:09 ` Steven Rostedt
2018-01-09 19:53 ` Peter Zijlstra
2018-01-11 9:13 ` Peter Zijlstra
2018-01-11 15:26 ` Vince Weaver
2018-01-11 15:38 ` Peter Zijlstra
2018-01-11 16:41 ` Vince Weaver
2018-01-11 16:58 ` Vince Weaver
2018-01-11 17:03 ` Peter Zijlstra
2018-01-11 18:04 ` Vince Weaver
2018-01-11 18:20 ` Vince Weaver
2018-01-11 19:01 ` Peter Zijlstra
2018-01-11 19:11 ` Peter Zijlstra
2018-01-11 20:15 ` Vince Weaver
2018-01-11 20:40 ` Vince Weaver
2018-01-11 20:57 ` Peter Zijlstra
2018-01-12 19:48 ` Vince Weaver
2018-01-11 20:42 ` Peter Zijlstra
2018-01-11 15:29 ` Peter Zijlstra
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=20180109162019.GL3040@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.weaver@maine.edu \
/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;
as well as URLs for NNTP newsgroup(s).