[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131118230553.32c478df@alan.etchedpixels.co.uk>
Date: Mon, 18 Nov 2013 23:05:53 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Vince Weaver <vincent.weaver@...ne.edu>
Cc: Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Paul Mackerras <paulus@...ba.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
tytso@....edu, adilger.kernel@...ger.ca
Subject: Re: perf bug: bad page map
On Mon, 18 Nov 2013 11:41:22 -0500 (EST)
Vince Weaver <vincent.weaver@...ne.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.
Obvious question - does it pass fsck currently. If it does then
presumably it was sane at the time it went pop ?
--
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