From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Petr Mladek <pmladek@suse.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Vince Weaver <vincent.weaver@maine.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"dvyukov@google.com" <dvyukov@google.com>
Subject: Re: perf: fuzzer BUG: KASAN: stack-out-of-bounds in __unwind_start
Date: Tue, 29 Nov 2016 12:07:11 -0800 [thread overview]
Message-ID: <20161129200711.GF3924@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161129195204.GG3045@worktop.programming.kicks-ass.net>
On Tue, Nov 29, 2016 at 08:52:04PM +0100, Peter Zijlstra wrote:
> On Tue, Nov 29, 2016 at 11:39:35AM -0800, Paul E. McKenney wrote:
> > On Tue, Nov 29, 2016 at 06:10:38PM +0100, Peter Zijlstra wrote:
>
> > > It mostly works, most of the time, and that seems to be what Linus
> > > wants, since its really the best we can have given the constraints. But
> > > for debugging, when you have a UART, it totally blows.
> >
> > UART??? They still make those things??? ;-)
>
> Yes, most computer like devices actually have them, trouble is, most
> consumer devices don't have the pins exposed. Luckily most server class
> hardware still does.
>
> And they're absolutely _awesome_ for debugging; getting data out is a
> matter of trivial MMIO poll loops. Rock solid stuff.
They very clearly need to bring the baud rate into the current millenium,
many tens of Mbaud at the -very- least.
Thanx, Paul
next prev parent reply other threads:[~2016-11-29 20:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 17:33 perf: fuzzer BUG: KASAN: stack-out-of-bounds in __unwind_start Vince Weaver
2016-11-28 21:54 ` Josh Poimboeuf
2016-11-29 0:40 ` Paul E. McKenney
2016-11-29 5:52 ` Josh Poimboeuf
2016-11-29 9:16 ` Peter Zijlstra
2016-11-29 14:07 ` Paul E. McKenney
2016-11-29 15:09 ` Josh Poimboeuf
2016-11-29 16:12 ` Petr Mladek
2016-11-29 18:01 ` Paul E. McKenney
2016-11-29 16:51 ` Paul E. McKenney
2016-11-29 17:17 ` Josh Poimboeuf
2016-11-29 17:36 ` Paul E. McKenney
2016-11-30 9:29 ` Petr Mladek
2016-11-29 10:28 ` Paul E. McKenney
2016-11-29 12:43 ` Peter Zijlstra
2016-11-29 15:10 ` Paul E. McKenney
2016-11-29 16:29 ` Petr Mladek
2016-11-29 17:10 ` Peter Zijlstra
2016-11-29 19:39 ` Paul E. McKenney
2016-11-29 19:52 ` Peter Zijlstra
2016-11-29 20:07 ` Paul E. McKenney [this message]
2016-11-29 20:32 ` Paul E. McKenney
2016-11-30 19:13 ` Josh Poimboeuf
2016-11-30 19:49 ` Paul E. McKenney
2016-12-01 5:52 ` Peter Zijlstra
2016-12-01 12:33 ` Paul E. McKenney
2016-12-01 16:41 ` Peter Zijlstra
2016-12-01 17:00 ` Paul E. McKenney
2016-11-30 10:01 ` Petr Mladek
2016-11-30 11:06 ` 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=20161129200711.GF3924@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=dvyukov@google.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--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).