[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikLv7xi4PF5j8dw9kFZbJaNR5utGbU3E=uBveFO@mail.gmail.com>
Date: Mon, 7 Mar 2011 20:14:22 +0200
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Felipe Contreras <felipe.contreras@...il.com>
Cc: Felipe Contreras <felipe.contreras@...ia.com>,
linux-main <linux-kernel@...r.kernel.org>,
linux-omap <linux-omap@...r.kernel.org>,
Greg KH <greg@...ah.com>,
Omar Ramirez Luna <omar.ramirez@...com>,
Fernando Guzman Lugo <fernando.lugo@...com>,
Nishanth Menon <nm@...com>,
Ameya Palande <ameya.palande@...ia.com>
Subject: Re: [PATCH] staging: tidspbridge: protect dmm_map properly
On Mon, Mar 7, 2011 at 8:02 PM, Felipe Contreras
<felipe.contreras@...il.com> wrote:
> On Mon, Dec 20, 2010 at 7:12 PM, Felipe Contreras
> <felipe.contreras@...ia.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.
Agree that a fix should be merged asap, and I don't mind which.
Especially since things have changed lately and chances that we will
use this code for OMAP4 too are really small now.
--
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/
Powered by blists - more mailing lists