Subject : 2.6.30 fb/mmap lockdep report.
Submitter : Dave Jones <email@example.com>
Date : 2009-06-21 13:33
References : http://lkml.org/lkml/2009/6/21/90
This entry is being used for tracking a regression from 2.6.29. Please don't
close it until the problem is fixed in the mainline.
Notify-Also : Jarek Poplawski <firstname.lastname@example.org>
References : http://lkml.org/lkml/2009/6/21/122
Author: Andrea Righi <email@example.com>
Date: Mon Apr 13 14:39:39 2009 -0700
fbdev: fix info->lock deadlock in fbcon_event_notify()
First-Bad-Commit : 513adb58685615b0b1d47a3f0d40f5352beff189
On Tuesday 07 July 2009, Jarek Poplawski wrote:
> On Tue, Jul 07, 2009 at 02:00:51AM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.29 and 2.6.30.
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.29 and 2.6.30. Please verify if it still should
> > be listed and let me know (either way).
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13647
> > Subject : fb/mmap lockdep report.
> > Submitter : Dave Jones <firstname.lastname@example.org>
> > Date : 2009-06-21 13:33 (16 days old)
> > First-Bad-Commit:
> > References : http://lkml.org/lkml/2009/6/21/90
> > http://lkml.org/lkml/2009/6/21/122
> This lockdep report isn't triggered by 2.6.31-rc2 anymore.