From: Dave Jones <davej@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, kosaki.motohiro@gmail.com, walken@google.com,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: mlockall triggred rcu_preempt stall.
Date: Tue, 30 Jul 2013 14:05:04 -0400 [thread overview]
Message-ID: <20130730180504.GA4546@redhat.com> (raw)
In-Reply-To: <20130730175718.GA8957@linux.vnet.ibm.com>
On Tue, Jul 30, 2013 at 10:57:18AM -0700, Paul E. McKenney wrote:
> On Fri, Jul 19, 2013 at 08:32:12PM -0400, Dave Jones wrote:
> > On Fri, Jul 19, 2013 at 03:15:39PM -0700, Paul E. McKenney wrote:
> > > On Fri, Jul 19, 2013 at 10:53:23AM -0400, Dave Jones wrote:
> > > > My fuzz tester keeps hitting this. Every instance shows the non-irq stack
> > > > came in from mlockall. I'm only seeing this on one box, but that has more
> > > > ram (8gb) than my other machines, which might explain it.
> > >
> > > Are you building CONFIG_PREEMPT=n? I don't see any preemption points in
> > > do_mlockall(), so a range containing enough vmas might well stall the
> > > CPU in that case.
> >
> > That was with full preempt.
> >
> > > Does the patch below help? If so, we probably need others, but let's
> > > first see if this one helps. ;-)
> >
> > I'll try it on Monday.
>
> Any news? If I don't hear otherwise, I will assume that the patch did
> not help, and will therefore drop it.
I wasn't able to do any tests yesterday, because I kept hitting other oopses.
I've got patches for the more obvious ones now, so I'll start testing rc3 this
afternoon.
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-07-30 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 14:53 mlockall triggred rcu_preempt stall Dave Jones
2013-07-19 22:15 ` Paul E. McKenney
2013-07-20 0:32 ` Dave Jones
2013-07-20 14:00 ` Paul E. McKenney
2013-07-30 17:57 ` Paul E. McKenney
2013-07-30 18:05 ` Dave Jones [this message]
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=20130730180504.GA4546@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=walken@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).