Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758536AbZJEMQQ (ORCPT ); Mon, 5 Oct 2009 08:16:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753919AbZJEMQQ (ORCPT ); Mon, 5 Oct 2009 08:16:16 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:54072 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753232AbZJEMQP (ORCPT ); Mon, 5 Oct 2009 08:16:15 -0400 Subject: Re: futex question From: Peter Zijlstra To: Thomas Gleixner Cc: Anirban Sinha , Ingo Molnar , linux-kernel@vger.kernel.org, Darren Hart , Kaz Kylheku , Anirban Sinha In-Reply-To: References: <20091001092218.GH15345@elte.hu> <4AC68F13.8050601@us.ibm.com> <4AC8CF32.8060108@anirban.org> <1254738974.26976.24.camel@twins> <1254743934.26976.42.camel@twins> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 05 Oct 2009 14:18:39 +0200 Message-Id: <1254745119.26976.43.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 741 Lines: 15 On Mon, 2009-10-05 at 13:59 +0200, Thomas Gleixner wrote: > Stared at the same place a minute ago :) But still I wonder if it's a > good idea to silently release locks and set the state to OWNERDEAD > instead of hitting the app programmer with a big clue stick in case > the app holds locks when calling execve(). Agreed, I rather like the feedback. With regular exit like things there's just not much we can do to avoid the mess, but here we can actually avoid it, seems a waste not to do so. -- 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/