linux-kernel - Re: commit 66c1ca breaks fbdev mode switching

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]

Date:	Mon, 6 Apr 2009 23:45:29 +0200
From:	Andrea Righi <righi.andrea@...il.com>
To:	Krzysztof Helt <krzysztof.h1@...zta.fm>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Andrey Borzenkov <arvidjaar@...il.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	"Antonino A. Daplas" <adaplas@...il.com>,
	linux-fbdev-devel@...ts.sourceforge.net,
	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Dave Jones <davej@...hat.com>,
	Harvey Harrison <harvey.harrison@...il.com>,
	Johannes Weiner <hannes@...xchg.org>,
	Stefan Richter <stefanr@...6.in-berlin.de>
Subject: Re: commit 66c1ca breaks fbdev mode switching

On Mon, Apr 06, 2009 at 08:47:18PM +0200, Krzysztof Helt wrote:
> Hi,
> 
> The commit 66c1ca breaks fbdev mode switching. The first mode
> (selected with mode_option or during boot) is ok but every mode
> switch with fbset locks up computer. If the commit is reverted
> mode switching works correctly.
> 
> I do not understand why. I would be grateful if someone else
> can confirm the problem as well.
> 
> The commit's details are:
> 
> commit 66c1ca019078220dc1bf968f2bb18421100ef147
> Author: Andrea Righi <righi.andrea@...il.com>
> Date:   Tue Mar 31 15:25:18 2009 -0700
> 
>     fbmem: fix fb_info->lock and mm->mmap_sem circular locking dependency
>     
> 
> Regards,
> Krzysztof

Any lockdep info or oops? it just locks up the system?

Thanks,
-Andrea
--
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/