All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Vince Weaver <vince@deater.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Oleg Nesterov <oleg@redhat.com>, Ben Myers <bpm@sgi.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	xfs@oss.sgi.com, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: splice vs execve lockdep trace.
Date: Tue, 16 Jul 2013 11:02:17 -0400	[thread overview]
Message-ID: <20130716150217.GA825@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1307160956370.15153@pianoman.cluster.toy>

On Tue, Jul 16, 2013 at 09:59:35AM -0400, Vince Weaver wrote:
 > On Mon, 15 Jul 2013, Linus Torvalds wrote:
 > 
 > > On Mon, Jul 15, 2013 at 7:38 PM, Dave Jones <davej@redhat.com> wrote:
 > > 
 > > > Interestingly, the 'soft lockups' I was
 > > > seeing all the time on that box seem to have gone into hiding.
 > > 
 > > Honestly, I'm somewhat inclined to blame the whole perf situation, and
 > > saying that we hopefully got that fixed. In between the silly do_div()
 > > buglets and all the indications that the time was spent in nmi
 > > handlers, I'd be willing to just ignore them as false positives
 > > brought on by the whole switch to the perf irq..
 > 
 > Did the perf soft lockups go away with 3.11-rc1?
 > 
 > 734df5ab549ca44f40de0f07af1c8803856dfb18 finally got committed,
 > and it fixes a major long-standing perf-related NMI soft lockup bug I 
 > found when fuzzing.

That could be it. I never got around to trying that commit standalone
when you first pointed it out.

thanks,

	Dave

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Vince Weaver <vince@deater.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Oleg Nesterov <oleg@redhat.com>, Ben Myers <bpm@sgi.com>,
	xfs@oss.sgi.com
Subject: Re: splice vs execve lockdep trace.
Date: Tue, 16 Jul 2013 11:02:17 -0400	[thread overview]
Message-ID: <20130716150217.GA825@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1307160956370.15153@pianoman.cluster.toy>

On Tue, Jul 16, 2013 at 09:59:35AM -0400, Vince Weaver wrote:
 > On Mon, 15 Jul 2013, Linus Torvalds wrote:
 > 
 > > On Mon, Jul 15, 2013 at 7:38 PM, Dave Jones <davej@redhat.com> wrote:
 > > 
 > > > Interestingly, the 'soft lockups' I was
 > > > seeing all the time on that box seem to have gone into hiding.
 > > 
 > > Honestly, I'm somewhat inclined to blame the whole perf situation, and
 > > saying that we hopefully got that fixed. In between the silly do_div()
 > > buglets and all the indications that the time was spent in nmi
 > > handlers, I'd be willing to just ignore them as false positives
 > > brought on by the whole switch to the perf irq..
 > 
 > Did the perf soft lockups go away with 3.11-rc1?
 > 
 > 734df5ab549ca44f40de0f07af1c8803856dfb18 finally got committed,
 > and it fixes a major long-standing perf-related NMI soft lockup bug I 
 > found when fuzzing.

That could be it. I never got around to trying that commit standalone
when you first pointed it out.

thanks,

	Dave

  reply	other threads:[~2013-07-16 15:02 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16  1:53 splice vs execve lockdep trace Dave Jones
2013-07-16  2:32 ` Linus Torvalds
2013-07-16  2:38   ` Dave Jones
2013-07-16  3:25     ` Linus Torvalds
2013-07-16  3:25       ` Linus Torvalds
2013-07-16  3:28       ` Dave Jones
2013-07-16  3:28         ` Dave Jones
2013-07-16  5:31       ` Al Viro
2013-07-16  5:31         ` Al Viro
2013-07-16  6:03       ` Dave Chinner
2013-07-16  6:03         ` Dave Chinner
2013-07-16  6:16         ` Al Viro
2013-07-16  6:16           ` Al Viro
2013-07-16  6:41           ` Dave Chinner
2013-07-16  6:41             ` Dave Chinner
2013-07-16  6:50           ` Dave Chinner
2013-07-16  6:50             ` Dave Chinner
2013-07-16 19:33         ` Ben Myers
2013-07-16 19:33           ` Ben Myers
2013-07-16 20:18           ` Linus Torvalds
2013-07-16 20:18             ` Linus Torvalds
2013-07-16 20:43             ` Dave Chinner
2013-07-16 20:43               ` Dave Chinner
2013-07-16 21:02               ` Linus Torvalds
2013-07-16 21:02                 ` Linus Torvalds
2013-07-17  4:06                 ` Dave Chinner
2013-07-17  4:06                   ` Dave Chinner
2013-07-17  4:54                   ` Linus Torvalds
2013-07-17  4:54                     ` Linus Torvalds
2013-07-17  5:51                     ` Dave Chinner
2013-07-17  5:51                       ` Dave Chinner
2013-07-17 16:03                       ` Linus Torvalds
2013-07-17 16:03                         ` Linus Torvalds
2013-07-17 23:40                         ` Ben Myers
2013-07-17 23:40                           ` Ben Myers
2013-07-18  0:17                           ` Linus Torvalds
2013-07-18  0:17                             ` Linus Torvalds
2013-07-18  3:42                             ` Dave Chinner
2013-07-18  3:42                               ` Dave Chinner
2013-07-18 21:16                               ` Ben Myers
2013-07-18 21:16                                 ` Ben Myers
2013-07-18 22:21                                 ` Ben Myers
2013-07-18 22:21                                   ` Ben Myers
2013-07-18 22:49                                   ` Dave Chinner
2013-07-18 22:49                                     ` Dave Chinner
2013-07-18  3:17                         ` Dave Chinner
2013-07-18  3:17                           ` Dave Chinner
2013-07-16 13:59       ` Vince Weaver
2013-07-16 13:59         ` Vince Weaver
2013-07-16 15:02         ` Dave Jones [this message]
2013-07-16 15:02           ` Dave Jones

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=20130716150217.GA825@redhat.com \
    --to=davej@redhat.com \
    --cc=bpm@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vince@deater.net \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xfs@oss.sgi.com \
    /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.