[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1308011158360.11550@pianoman.cluster.toy>
Date: Thu, 1 Aug 2013 12:02:06 -0400 (EDT)
From: Vince Weaver <vince@...ter.net>
To: Dave Jones <davej@...hat.com>
cc: Olof Johansson <olof@...om.net>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Aaro Koskinen <aaro.koskinen@....fi>,
"ksummit-2013-discuss@...ts.linuxfoundation.org"
<ksummit-2013-discuss@...ts.linuxfoundation.org>,
Kees Cook <keescook@...omium.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2013-discuss] [ARM ATTEND] catching up on exploit
mitigations
On Wed, 31 Jul 2013, Dave Jones wrote:
> On Wed, Jul 31, 2013 at 07:47:30PM -0700, Olof Johansson wrote:
> > How long would a useful run of trinity take?
>
> It blew up in a minute or so of runtime when I tried last week.
I also have a chromebook running 3.4 and it is trivially easy to crash it
with some simple perf_event tests I have (not the fuzzer, but just the
regular validation tests that test counter overflow).
Like Dave, I didn't bother reporting the problem because I figured 3.4 was
too old for anyone to care about and it was a struggle getting any
distro/kernel installed at all on the system let alone trying to boot
something close to current mainline on it.
Vince
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists