From: Dave Jones <davej@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Sasha Levin <levinsasha928@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Linux 3.6-rc4
Date: Fri, 21 Sep 2012 17:16:39 -0400 [thread overview]
Message-ID: <20120921211639.GA17379@redhat.com> (raw)
In-Reply-To: <1347287780.2124.10.camel@twins>
On Mon, Sep 10, 2012 at 04:36:20PM +0200, Peter Zijlstra wrote:
> On Fri, 2012-09-07 at 11:39 -0700, Linus Torvalds wrote:
> > Al? Please look into this. I'm not entirely sure what's going on, but
> > lockdep complains about this:
> >
> > Possible interrupt unsafe locking scenario:
> >
> > CPU0 CPU1
> > ---- ----
> > lock(&(&p->alloc_lock)->rlock);
> > local_irq_disable();
> > lock(&(&new_timer->it_lock)->rlock);
> > lock(tasklist_lock);
> > <Interrupt>
> > lock(&(&new_timer->it_lock)->rlock);
> >
> > *** DEADLOCK ***
> >
> > and it looks real. IOW, if I read that right, we have the task_lock ->
> > it_lock dependency through exit_itimers(), and then we have the
> > tasklist_lock -> task_lock dependency everywhere else. So now it_lock
> > -> tasklist_lock becomes a deadlock.
>
> Agreed, I've got the following series from Oleg queued to solve this:
>
> http://marc.info/?l=linux-kernel&m=134600821828491&w=2
What's happening with this series ? I'm still seeing these traces in rc6.
Dave
next prev parent reply other threads:[~2012-09-21 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 22:10 Linux 3.6-rc4 Linus Torvalds
2012-09-04 15:44 ` Dave Jones
2012-09-07 17:55 ` Sasha Levin
2012-09-07 18:39 ` Linus Torvalds
2012-09-10 14:36 ` Peter Zijlstra
2012-09-15 12:25 ` Sasha Levin
2012-09-21 21:16 ` Dave Jones [this message]
2012-09-28 19:05 ` Dave Jones
2012-10-01 20:55 ` Linus Torvalds
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=20120921211639.GA17379@redhat.com \
--to=davej@redhat.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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