Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753879Ab1DNV5G (ORCPT ); Thu, 14 Apr 2011 17:57:06 -0400 Received: from kroah.org ([198.145.64.141]:52091 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752980Ab1DNV5D (ORCPT ); Thu, 14 Apr 2011 17:57:03 -0400 Date: Thu, 14 Apr 2011 14:56:56 -0700 From: Greg KH To: Darren Hart Cc: Linux Kernel Mailing List , Eric Dumazet , Peter Zijlstra , Linux Stable , John Kacur , Ingo Molnar , Thomas Gleixner Subject: Re: [stable] [PATCH V4] futex: set FLAGS_HAS_TIMEOUT during demux for FUTEX_WAIT Message-ID: <20110414215656.GB14169@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1463 Lines: 36 On Thu, Apr 14, 2011 at 02:43:01PM -0700, Darren Hart wrote: > The FLAGS_HAS_TIMEOUT flag was not getting set, causing the restart_block to > restart futex_wait() without a timeout after a signal. > > Commit b41277dc7a18ee332d in 2.6.38 introduced the regression by accidentally > removing the the FLAGS_HAS_TIMEOUT assignment from futex_wait() during the setup > of the restart block. Restore the originaly behavior. > > Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=32922 > > V2: Added references to commit message. > V3: Set flag during restart block instead of do_futex() > V4: Correct stupid order of assignment mistake pointed out by Eric > > Signed-off-by: Darren Hart > Reported-by: Tim Smith > Reported-by: Torsten Hilbrich > Cc: Thomas Gleixner > Cc: Peter Zijlstra > Cc: Ingo Molnar > CC: Eric Dumazet > CC: John Kacur > --- This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read Documentation/stable_kernel_rules.txt for how to do this properly. thanks, 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/