From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
tytso@mit.edu, adilger.kernel@dilger.ca
Subject: Re: perf bug: bad page map
Date: Mon, 18 Nov 2013 23:05:53 +0000 [thread overview]
Message-ID: <20131118230553.32c478df@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <alpine.DEB.2.10.1311181138390.18020@vincent-weaver-1.um.maine.edu>
On Mon, 18 Nov 2013 11:41:22 -0500 (EST)
Vince Weaver <vincent.weaver@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.
Obvious question - does it pass fsck currently. If it does then
presumably it was sane at the time it went pop ?
next prev parent reply other threads:[~2013-11-18 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 18:04 Vince Weaver
2013-11-18 15:17 ` Peter Zijlstra
2013-11-18 15:36 ` Ingo Molnar
2013-11-18 16:41 ` Vince Weaver
2013-11-18 17:13 ` Ingo Molnar
2013-11-18 23:05 ` One Thousand Gnomes [this message]
2013-11-19 1:57 ` Vince Weaver
2013-11-19 7:06 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131118230553.32c478df@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=acme@ghostprotocols.net \
--cc=adilger.kernel@dilger.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tytso@mit.edu \
--cc=vincent.weaver@maine.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®