linux-kernel - [REGRESSION] commit 66c1ca0: {fbmem: fix fb_info->lock and mm->mmap

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-next>] [day] [month] [year] [list]

Date:	Thu, 9 Apr 2009 19:36:24 +0800
From:	Eric Miao <eric.y.miao@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Andrea Righi <righi.andrea@...il.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Krzysztof Helt <krzysztof.h1@...zta.fm>
Subject: [REGRESSION] commit 66c1ca0: {fbmem: fix fb_info->lock and 
	mm->mmap_sem ...} causes Xfbdev not working

This happens on my Marvell PXA310-based Littleton platform with
Angstrom Distribution. The offending paths are many:

FBIOPUT_VSCREENINFO:
  lock_fb_info()
  --> fb_set_var()
    --> fb_notifier_call_chain() [FBINFO_MISC_USEREVENT]
      --> fbcon_event_notifier() [FB_EVENT_MODE_CHANGE]
        --> lock_fb_info()

OK, now hang. I'd suggest a clean fix to the original assumption of
circular locking
issue and revert this commit first.

-- 
Cheers
- eric
--
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/