mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: sedat.dilek@gmail.com
Cc: Jiri Kosina <jkosina@suse.cz>,
	linux-fbdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	alan@lxorguk.ukuu.org.uk,
	Andrew Morton <akpm@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.cz>
Subject: Re: 3.8-rc2 lockdep complains about console_lock vs. fb_notifier_list.rwsem
Date: Wed, 16 Jan 2013 10:35:12 +0100	[thread overview]
Message-ID: <s5hpq1531yn.wl%tiwai@suse.de> (raw)
In-Reply-To: <CA+icZUWFKzccbHrU0pxK-T2TdwyDsTTNxP_22zmGTPbcAmhMaQ@mail.gmail.com>

At Wed, 16 Jan 2013 10:21:46 +0100,
Sedat Dilek wrote:
> 
> On Tue, Jan 15, 2013 at 3:25 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > At Sat, 5 Jan 2013 13:13:27 +0100,
> > Sedat Dilek wrote:
> >>
> >> Hi Jiri,
> >>
> >> ...known issue (see thread in [1]), please feel free to test patches
> >> from Alan and Andrew (see [1], [2] and [3]) and report.
> >>
> >> Regards,
> >> - Sedat -
> >>
> >> [1] http://marc.info/?t=135309396400003&r=1&w=2
> >> [2] http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover.patch
> >> [3] http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover-fix.patch
> >> [4] http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover-fix-2.patch
> >
> > I've hit this bug and tried the patch [2] ([3] and [4] are gone).
> > Unfortunately the deadlock is still reported, as seen below.
> >
> > A similar fix for fbcon_unbind(), splitting an unlocked version of
> > unbind_con_driver() and call it?
> >
> > (BTW, the patch [2] contains strange characters in the comments, and
> >  has a few coding issues easily detected by checkpatch.pl.)
> >
> 
> [ CCing Rafael as he asked in another thread if I had sent a patch ]
> 
> I noticed also some these "strange" chars in the patch from Andrew and
> a patch of mine was sent as
> "fb-Rework-locking-to-fix-lock-ordering-on-takeover-fix-comments.patch"
> to the lists.
> 
> It is strange to me that Andrew or other maintainers himself did not
> check with "checkpatch.pl".
> This should be a common testcase!
> Hey, noone is perfect :-).
> ( /me has also not checked with that script - I just saw it. )
> 
> Just as a note to the issue in general:
> Andrew took over the patch from Alan which is very honest - he is not
> the active TTY maintainer!
> Didn't Greg takeover maintenance from Alan (after a dispute and blaming Alan)?
> If this is true, why the hell is Greg not CCed?

Let's do it :)

Greg, Jiri, this bug hits already quite a few people.

I can reproduce the bug easily on a machine with a radeon graphics.
It appears always at boot when lockdep is enabled.


> Thanks for the real patch in the followup of this thread!
> Who will take care of it :-)?

Either tty maintainer, or fb maintainer, or Andrew?

FWIW, Andrew took my patch in mm:
  http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover.patch
  http://ozlabs.org/~akpm/mmots/broken-out/fb-yet-another-band-aid-for-fixing-lockdep-mess.patch


thanks,

Takashi

  reply	other threads:[~2013-01-16  9:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 12:13 Sedat Dilek
2013-01-15 14:25 ` Takashi Iwai
2013-01-15 14:47   ` Takashi Iwai
2013-01-15 16:46     ` Takashi Iwai
2013-01-16  9:21   ` Sedat Dilek
2013-01-16  9:35     ` Takashi Iwai [this message]
2013-01-16  9:52       ` Sedat Dilek
2013-01-16  9:59         ` Sedat Dilek
2013-01-16 11:07           ` Sedat Dilek
2013-01-16 12:51             ` Sedat Dilek
2013-01-17  2:42       ` Greg Kroah-Hartman
2013-01-17  3:54         ` Andrew Morton
2013-01-17  4:16           ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2013-01-05 11:08 Jiri Kosina

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=s5hpq1531yn.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=jslaby@suse.cz \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=sedat.dilek@gmail.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®