Messages in this thread | | | Date | Mon, 7 Mar 2011 13:29:02 -0600 | Subject | Re: [PATCH] staging: tidspbridge: protect dmm_map properly | From | "Ramirez Luna, Omar" <> |
| |
Hi Felipe,
On Mon, Mar 7, 2011 at 12:02 PM, Felipe Contreras <felipe.contreras@gmail.com> wrote: > On Mon, Dec 20, 2010 at 7:12 PM, Felipe Contreras > <felipe.contreras@nokia.com> wrote: >> 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. This patch fixes those. > > I just heard that Tuomas Kulve is getting a lot of panics on Gumstix > Overo. I propose we apply this patch on the stable tree ASAP, and if > there's no better proposals, also on .38.
Can you or Tuomas share the bug report data (panic log, test case maybe)? I would like to discard issues affected by timing that could be hidden with this patch.
I agree that for the time being this needs to be sent upstream, even if in paper Ohad's patch solves the issue without side effects of locking.
Thanks,
Omar
| |