diff options
| author | Paul Mundt <lethal@linux-sh.org> | 2009-07-03 15:45:56 +0900 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-07-04 10:39:06 -0700 |
| commit | f50bf2b2f5e83b794e0bdb2f3f589f55ef0d52d0 (patch) | |
| tree | 01020b4eaa2df173889ebcfb71f7dc02097dede6 /Makefile | |
| parent | de481ba925e880764e38b8756c93c05006892507 (diff) | |
| download | linux-f50bf2b2f5e83b794e0bdb2f3f589f55ef0d52d0.tar.gz linux-f50bf2b2f5e83b794e0bdb2f3f589f55ef0d52d0.tar.bz2 linux-f50bf2b2f5e83b794e0bdb2f3f589f55ef0d52d0.zip | |
video: sm501fb: Early initialization of mm_lock mutex.
Commit 537a1bf059fa312355696fa6db80726e655e7f17 (fbdev: add mutex for
fb_mmap locking) introduces a ->mm_lock mutex for protecting smem
assignments. Unfortunately in the case of sm501fb these happen quite
early in the initialization code, well before the mutex_init() that takes
place in register_framebuffer(), leading to:
Badness at kernel/mutex.c:207
Pid : 1, Comm: swapper
CPU : 0 Not tainted (2.6.31-rc1-00284-g529ba0d-dirty #2273)
PC is at __mutex_lock_slowpath+0x72/0x1bc
PR is at __mutex_lock_slowpath+0x66/0x1bc
...
matroxfb appears to have the same issue and has solved it with an early
mutex_init(), so we do the same for sm501fb.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Cc: Krzysztof Helt <krzysztof.h1@wp.pl>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions