Re: [RESEND PATCH 1/2] fb: reorder the lock sequence to fix potential dead lock

Hi Tomi, On 11/11/2013 09:59 PM, Tomi Valkeinen wrote: > On 2013-11-05 12:00, Gu Zheng wrote: >> Following commits: >> 50e244cc79 fb: rework locking to fix lock ordering on takeover >> e93a9a8687 fb: Yet another band-aid for fixing lockdep mess >> 054430e773 fbcon: fix locking harder >> reworked l

Re: [RESEND PATCH 1/2] fb: reorder the lock sequence to fix potential dead lock

On 2013-11-05 12:00, Gu Zheng wrote: > Following commits: > 50e244cc79 fb: rework locking to fix lock ordering on takeover > e93a9a8687 fb: Yet another band-aid for fixing lockdep mess > 054430e773 fbcon: fix locking harder > reworked locking to fix related lock ordering on takeover, and introduced

[RESEND PATCH 1/2] fb: reorder the lock sequence to fix potential dead lock

Following commits: 50e244cc79 fb: rework locking to fix lock ordering on takeover e93a9a8687 fb: Yet another band-aid for fixing lockdep mess 054430e773 fbcon: fix locking harder reworked locking to fix related lock ordering on takeover, and introduced console_lock into fbmem, but it seems that th

[PATCH 1/2] fb: reorder the lock sequence to fix potential dead lock

Following commits: 50e244cc79 fb: rework locking to fix lock ordering on takeover e93a9a8687 fb: Yet another band-aid for fixing lockdep mess 054430e773 fbcon: fix locking harder reworked locking to fix related lock ordering on takeover, and introduced console_lock into fbmem, but it seems that th