Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755517Ab1CGSuF (ORCPT ); Mon, 7 Mar 2011 13:50:05 -0500 Received: from kroah.org ([198.145.64.141]:53052 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752918Ab1CGSuD (ORCPT ); Mon, 7 Mar 2011 13:50:03 -0500 Date: Mon, 7 Mar 2011 10:48:00 -0800 From: Greg KH To: Felipe Contreras Cc: Felipe Contreras , linux-main , linux-omap , Omar Ramirez Luna , Ohad Ben-Cohen , Fernando Guzman Lugo , Nishanth Menon , Ameya Palande Subject: Re: [PATCH] staging: tidspbridge: protect dmm_map properly Message-ID: <20110307184800.GA13355@kroah.com> References: <1292865120-24020-1-git-send-email-felipe.contreras@nokia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1139 Lines: 26 On Mon, Mar 07, 2011 at 08:02:44PM +0200, Felipe Contreras wrote: > On Mon, Dec 20, 2010 at 7:12 PM, Felipe Contreras > 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. Um, I don't think you realize _how_ stable trees work, please go read Documentation/stable_kernel_rules.txt to see how it is not possible to take something into the stable releases before it goes to Linus's tree. Sorry, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/