Re: tracing ring_buffer_resize oops.

[Dave Jones]

On Thu, May 24, 2012 at 04:33:06PM -0400, Steven Rostedt wrote:

 > I'm kicking off the ktest that initially caused this issue hoping that
 > it reproduces the bad tree again.
 > 
 > BTW, did you happen to upgrade gcc or anything? The ktest I run does
 > test against different gcc's and I don't think I had it do a make clean
 > between the switch. That may be the cause of this problem too :-?

No gcc updates. It's a Fedora 17 box, so there's been hardly any updates this
last week or so as things have been frozen leading into the release.

	Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/