Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753558Ab0L1Mhs (ORCPT ); Tue, 28 Dec 2010 07:37:48 -0500 Received: from mail-iy0-f174.google.com ([209.85.210.174]:52604 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753099Ab0L1Mhr (ORCPT ); Tue, 28 Dec 2010 07:37:47 -0500 MIME-Version: 1.0 X-Originating-IP: [93.172.188.89] In-Reply-To: References: <1292870624-25450-1-git-send-email-felipe.contreras@nokia.com> <1293452486-notmuch-felipe.contreras@nokia.com> From: Ohad Ben-Cohen Date: Tue, 28 Dec 2010 14:37:26 +0200 Message-ID: Subject: Re: [PATCH v2] staging: tidspbridge: protect dmm_map properly To: Felipe Contreras Cc: Felipe Contreras , linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, greg@kroah.com, omar.ramirez@ti.com, fernando.lugo@ti.com, nm@ti.com, ameya.palande@nokia.com, h-kanigeri2@ti.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 966 Lines: 23 On Tue, Dec 28, 2010 at 2:24 PM, Felipe Contreras wrote: > user-space crashed, not kernel-space; the code would continue to run > and eventually release the lock. So you'll have to be more specific about the scenario you are describing. If there's a user thread that is still running the proc_*_dma() function, and we agree that this thread keeps running until completion and then returns to user space, what's the problem ? If that user thread will crash, drv_remove_all_resources() will clean up all map_obj's. > Yeah, so the chances of getting this fixed on 2.6.37 are dimmed. I wouldn't worry about that.. In the worst case, "Cc: stable@kernel.org" will push the fix into 2.6.37.x.. -- 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/