[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1307021628510.8353@vincent-weaver-1.um.maine.edu>
Date: Tue, 2 Jul 2013 16:32:42 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: Vince Weaver <vincent.weaver@...ne.edu>
cc: Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
trinity@...r.kernel.org
Subject: Re: [testcase] perf: yet another fuzzer triggered crash
On Mon, 1 Jul 2013, Vince Weaver wrote:
> I'm in the process of kernel bisecting this, though all I can tell you so
> far is 2.6.32 is unaffected by the bug but 3.2 and later are.
well, I spent 2 days bisecting between 3.1 and 3.2 (after
wasting time bisecting between 3.0 and 3.1 by mistake)
(also, a pox on whoever introduced that ethernet .config change between
3.1. 3.2).
and of course what it gives me is
a240f76165e6255384d4bdb8139895fac7988799
perf, core: Introduce attrs to count in either host or guest mode
so the test case wasn't crashing because the auto-generated file
was setting exclude_guest and exclude_host causing perf_event_open()
to fail. If I drop setting those bits it still crashes.
I guess back to the drawing board.
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