From: Russell King <rmk@arm.linux.org.uk>
To: Dave Airlie <airlied@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Andrew Morton <akpm@linux-foundation.org>,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: BUG: circular locking dependency detected
Date: Thu, 31 Jan 2013 00:13:40 +0000 [thread overview]
Message-ID: <20130131001339.GC14801@flint.arm.linux.org.uk> (raw)
In-Reply-To: <CAPM=9tz6YBh2o3T8Ogt4K=wxSrC3Jc4PCJMzfpbyY=B132fA5g@mail.gmail.com>
On Thu, Jan 31, 2013 at 10:04:05AM +1000, Dave Airlie wrote:
> On Thu, Jan 31, 2013 at 9:52 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > On Thu, Jan 31, 2013 at 9:19 AM, Russell King <rmk@arm.linux.org.uk> wrote:
> >>
> >> So... what you seem to be telling me is that 3.9 is going to be a
> >> release which issues lockdep complaints when the console blanks, and
> >> you think that's acceptable?
> >>
> >> Adding Linus and Andrew so they're aware of this issue...
> >
> > Oh, we're extremely aware of it. And it's not a new issue, the locking
> > problem have apparently been around forever, although I'm not sure why
> > the lockdep splat itself started happening only recently.
> >
> > They'll make it into 3.9, it's 3.8 that won't have them. The patches
> > initially caused way *worse* behavior than just a lockdep splat - they
> > caused actual hard lockups (and that was *after* the initial series of
> > fixes). That got fixed (hopefully for the last case!) fairly recently,
> > and I'm not willing to take the scary patch-series that has had
> > several problem cases.
>
> Well we didn't have any lock validation support before Daniel added it
> a couple of kernels back,
> so instead of hidden locking problems we've had from time began, we now have
> lockdep detectable locking problems.
Which may or may not be a good thing depending how you look at it; it
means that once your kernel blanks, you get a lockdep dump. At that
point you lose lockdep checking for everything else because lockdep
disables itself after the first dump.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2013-01-31 0:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 20:04 BUG: circular locking dependency detected Russell King
2013-01-30 20:06 ` Russell King
2013-01-30 20:06 ` Russell King
2013-01-30 21:52 ` Russell King
2013-01-30 21:52 ` Russell King
2013-01-30 22:07 ` Daniel Vetter
2013-01-30 22:07 ` Daniel Vetter
2013-01-30 22:19 ` Russell King
2013-01-30 22:19 ` Russell King
2013-01-30 22:19 ` Russell King
2013-01-30 22:27 ` Daniel Vetter
2013-01-30 22:27 ` Daniel Vetter
2013-01-30 23:52 ` Linus Torvalds
2013-01-30 23:52 ` Linus Torvalds
2013-01-31 0:04 ` Dave Airlie
2013-01-31 0:04 ` Dave Airlie
2013-01-31 0:13 ` Russell King [this message]
2013-01-31 0:26 ` Linus Torvalds
2013-01-31 0:26 ` Linus Torvalds
2013-01-31 5:40 ` Greg Kroah-Hartman
2013-01-31 5:40 ` Greg Kroah-Hartman
2013-01-31 8:21 ` Daniel Vetter
2013-01-31 8:21 ` Daniel Vetter
2013-01-31 9:21 ` Greg Kroah-Hartman
2013-01-31 9:21 ` Greg Kroah-Hartman
2013-01-31 9:38 ` Daniel Vetter
2013-01-31 9:38 ` Daniel Vetter
2013-01-31 11:51 ` Dave Airlie
2013-01-31 11:51 ` Dave Airlie
2013-01-31 13:02 ` Greg Kroah-Hartman
2013-01-31 13:02 ` Greg Kroah-Hartman
2013-01-31 13:07 ` Russell King
2013-01-31 0:09 ` Russell King
2013-01-31 10:12 ` Sedat Dilek
2013-01-31 10:12 ` Sedat Dilek
2013-01-31 10:20 ` Sedat Dilek
2013-01-31 10:20 ` Sedat Dilek
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=20130131001339.GC14801@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=FlorianSchandinat@gmx.de \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.