* Vince Weaver <vincent.wea...@maine.edu> wrote:
> On Mon, 18 Nov 2013, Peter Zijlstra wrote:
>
> > On Fri, Nov 15, 2013 at 01:04:23PM -0500, Vince Weaver wrote:
> > >
> > > (figured out the minicom issue).
> > >
> > > Anyway while trying to reproduce the last bug I instead got this with
> > > the perf_fuzzer.
> > >
> > > Is it worth continuing to run and report these issues? I'm losing track
> > > of all the open bugs.
> >
> > This is looks like ext4. Not entirely sure how perf ties into this.
>
> It's believable the filesystem could have issues (it's a fuzzer
> machine, so it's had 100+ unclean shutdowns on an SSD drive in the
> past few months) but as far as I know there shouldn't have been any
> filesystem accesses happening at all when the bug triggered.
>
> I thought it might be perf related due to the perf references in the
> backtrace (and since it was being perf-fuzzed at the time).
Maybe the connection is that ext4 has lots of tracepoints?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
