mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Dave Jones <davej@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: sched: circular dependency between sched_domains_mutex and oom_notify_list
Date: Mon, 18 Feb 2013 09:26:39 +0100	[thread overview]
Message-ID: <20130218082639.GA15989@gmail.com> (raw)
In-Reply-To: <51206DAB.7030701@oracle.com>


* Sasha Levin <sasha.levin@oracle.com> wrote:

> I suspect it's the result of adding the new rcu_oom_notify, but that happened
> about half a year ago so I'm not sure why this showed up only now.
> 
> [ 1039.634183] ======================================================
> [ 1039.635717] [ INFO: possible circular locking dependency detected ]
> [ 1039.637255] 3.8.0-rc7-next-20130215-sasha-00003-gea816fa #286 Tainted: G        W
> [ 1039.639104] -------------------------------------------------------
> [ 1039.640579] init/1 is trying to acquire lock:
> [ 1039.641224]  ((oom_notify_list).rwsem){.+.+..}, at: [<ffffffff81141c8f>] __blocking_notifier_call_chain+0x7f/0xc0

We changed (optimized) rwsems via:

 3a15e0e0cdda rwsem: Implement writer lock-stealing for better scalability

so maybe it can hit different codepaths and races now?

Thanks,

	Ingo

  reply	other threads:[~2013-02-18  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17  5:42 Sasha Levin
2013-02-18  8:26 ` Ingo Molnar [this message]
2013-02-19  0:32   ` Sasha Levin
2013-02-19  4:48 ` Michael Wang
2013-02-19  8:58   ` Michael Wang

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=20130218082639.GA15989@gmail.com \
    --to=mingo@kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=sasha.levin@oracle.com \
    --cc=tglx@linutronix.de \
    /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
Powered by JetHome