All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
	LKML <linux-kernel@vger.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 16:36:29 +0100	[thread overview]
Message-ID: <20131118153629.GA28679@gmail.com> (raw)
In-Reply-To: <20131118151746.GC10022@twins.programming.kicks-ass.net>


* Peter Zijlstra <peterz@infradead.org> 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.
> 
> Anyway, yes, I do think its useful to keep running these tests, we 
> do fix various issues -- although probably not at the rate you seem 
> to be finding them.

I'm trying to slow down the merging of kernel side features, so that 
the fixing effort has a chance to catch up...

Thanks,

	Ingo

  reply	other threads:[~2013-11-18 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 18:04 perf bug: bad page map Vince Weaver
2013-11-18 15:17 ` Peter Zijlstra
2013-11-18 15:36   ` Ingo Molnar [this message]
2013-11-18 16:41   ` Vince Weaver
2013-11-18 17:13     ` Ingo Molnar
2013-11-18 23:05     ` One Thousand Gnomes
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=20131118153629.GA28679@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@ghostprotocols.net \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.