linux-kernel - Re: tty, vt: lockdep warnings (Patch v3)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <509D5C97.2020801@oracle.com>
Date:	Fri, 09 Nov 2012 14:42:15 -0500
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Hugh Dickins <hughd@...gle.com>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Bjørn Mork <bjorn@...k.no>,
	Sasha Levin <levinsasha928@...il.com>,
	Dave Jones <davej@...hat.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jiri Slaby <jslaby@...e.cz>, linux-kernel@...r.kernel.org,
	linux-fbdev@...r.kernel.org, florianSchandinat@....de
Subject: Re: tty, vt: lockdep warnings (Patch v3)

On 11/09/2012 02:34 PM, Hugh Dickins wrote:
> On Thu, 8 Nov 2012, Alan Cox wrote:
>> commit f35b3fbf24c4e4debb6a7a864b09854ccc2a22e7
>> Author: Alan Cox <alan@...ux.intel.com>
>> Date:   Wed Nov 7 16:35:08 2012 +0000
>>
>>     fb: Rework locking to fix lock ordering on takeover
>>     
>>     Adjust the console layer to allow a take over call where the caller already
>>     holds the locks. Make the fb layer lock in order.
>>     
>>     This s partly a band aid, the fb layer is terminally confused about the
>>     locking rules it uses for its notifiers it seems.
>>     
>>     Signed-off-by: Alan Cox <alan@...ux.intel.com>
> 
> This version works for me too - thanks.
> Hugh

I was planning to test it last night, but new code in mm/ failed horribly and
was BUG()ing all over the place, so I didn't get any significant testing
of this patch done.

Will update...


Thanks,
Sasha

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/