mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Alexander E. Patrakov" <patrakov@gmail.com>
Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: BUG: sleeping function called from invalid context at kernel/mutex.c:271
Date: Wed, 18 Apr 2012 08:08:46 -0400	[thread overview]
Message-ID: <1334750926.28106.36.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1334724679.2019.20.camel@aep-desktop>

On Wed, 2012-04-18 at 10:51 +0600, Alexander E. Patrakov wrote:

> > > 
> > > Hmm, this can also be reported if you have an rcu leak. Which would also
> > > explain your memory leak. RCU is the kernel's "garbage collector" and if
> > > it gets stuck, then you will definitely start seeing memory leaks, as
> > > memory wont be freed.
> > 
> > If RCU is stuck, you should see RCU CPU stall warnings, which can
> > give clues as to what is causing RCU to get stuck.
> 
> Yes, there were such warnings, but all of them said that the stall ended
> before dump start. So nothing reportable here, but I have just found
> that https://bugzilla.novell.com/show_bug.cgi?id=754186 looks quite
> similar in the sense that it (and duplicates) also has undumpable stalls
> of increasing length, and IPv6 is in use both at home and at work.
> 

Do you see the RT throttling message too? That's a bug with an RT task
going haywire. If that is happening, an RT task may be preventing an RCU
grace period to finish, and causing the RCU stalls.

Just because they ended, doesn't mean that the problem went a way. If
RCU is being blocked, you will start to see memory leaks. As I said, RCU
works as the kernels garbage collector. If it stops or just slows down
significantly, memory does not get freed.

-- Steve



  reply	other threads:[~2012-04-18 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  7:27 Alexander E. Patrakov
2012-04-18  2:56 ` Steven Rostedt
2012-04-18  4:06   ` Paul E. McKenney
2012-04-18  4:51     ` Alexander E. Patrakov
2012-04-18 12:08       ` Steven Rostedt [this message]
2012-04-18 13:45         ` Alexander E. Patrakov
2012-04-18 13:48           ` Steven Rostedt
2012-04-18 15:21             ` Alexander E. Patrakov
2012-04-18 16:19               ` Alexander E. Patrakov
2012-04-18 13:51         ` Paul E. McKenney

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=1334750926.28106.36.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrakov@gmail.com \
    --cc=paulmck@linux.vnet.ibm.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

all inboxes | Powered by JetHome®