staging: tidspbridge: protect dmm_map properly
authorFelipe Contreras <felipe.contreras@nokia.com>
Sat, 12 Mar 2011 00:29:06 +0000 (18:29 -0600)
committerGreg Kroah-Hartman <gregkh@suse.de>
Mon, 14 Mar 2011 19:22:27 +0000 (12:22 -0700)
commitab42abf33a3efdf754710a0a513c00c40854cd61
treea8c7a9aa9b6cab93b767caed5bfaf4b318711e8b
parent17e2a542032f3ab735352d1d4b5d2ca3c154158a
staging: tidspbridge: protect dmm_map properly

We need to protect not only the dmm_map list, but the individual
map_obj's, otherwise, we might be building the scatter-gather list with
garbage. So, use the existing proc_lock for that.

I observed race conditions which caused kernel panics while running
stress tests, also, Tuomas Kulve found it happening quite often in
Gumstix Over. This patch fixes those.

Cc: Tuomas Kulve <tuomas@kulve.fi>
Signed-off-by: Felipe Contreras <felipe.contreras@nokia.com>
Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/staging/tidspbridge/rmgr/proc.c