[Ksummit-2013-discuss] [ARM ATTEND] catching up on exploit mitigations
davej at redhat.com
Wed Jul 31 22:59:11 EDT 2013
On Wed, Jul 31, 2013 at 07:47:30PM -0700, Olof Johansson wrote:
> > > Hmm, really? Did you reported these bugs? I'm not aware of mainline
> > > having any changes related to bug reports on PTEs on ARM.
> > I wasn't sure if it was a googleism, or happens on mainline, so no.
> As of 3.10, it's not actually hard to run a mainline kernel on the
> chromebook, but you have limited functionality (no wifi, no USB3, no
> accellerated graphics). Easiest is to do it by booting from SD card.
> See instructions at
Yeah, that's how I got Fedora running on it (I think the people who did the
Fedora spin for the chromebook chose the google kernel for exactly
the reasons you mention above). It felt a little sluggish for a native
kernel build though, and I'm not setup for cross-building so I stuck with
the 3.4 build.
> 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've got an autobuilder/autobooter setup here with a cross-section of current ARM
> hardware (7 platforms and counting) that I mostly do boot testing on,
> and I should add a smallish suite of testcases to the same. Trinity
> would be a good candidate for that.
Feel free to mail me off-list if I can do anything to help out, though
hopefully things should build & run 'out of the box'. You shouldn't
need any special command line args (though you might get inspiration
for ideas from the scripts/test-* harnesses)
More information about the linux-arm-kernel