Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754131Ab0GLKgK (ORCPT ); Mon, 12 Jul 2010 06:36:10 -0400 Received: from www.tglx.de ([62.245.132.106]:33738 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752305Ab0GLKgI (ORCPT ); Mon, 12 Jul 2010 06:36:08 -0400 Date: Mon, 12 Jul 2010 12:35:00 +0200 (CEST) From: Thomas Gleixner To: Darren Hart cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Eric Dumazet , John Kacur , Steven Rostedt , Mike Galbraith , linux-rt-users@vger.kernel.org Subject: Re: [PATCH 3/4] futex: free_pi_state outside of hb->lock sections In-Reply-To: <1278714780-788-4-git-send-email-dvhltc@us.ibm.com> Message-ID: References: <1278714780-788-1-git-send-email-dvhltc@us.ibm.com> <1278714780-788-4-git-send-email-dvhltc@us.ibm.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1205 Lines: 38 On Fri, 9 Jul 2010, Darren Hart wrote: > free_pi_state() calls kfree() and might sleep. To prepare for raw hb->locks, > get the calls to free_pi_state() out of the hb->lock() sections. > > Signed-off-by: Darren Hart > Cc: Thomas Gleixner > Cc: Peter Zijlstra > Cc: Ingo Molnar > Cc: Eric Dumazet > Cc: John Kacur > Cc: Steven Rostedt > Cc: Mike Galbraith > --- > kernel/futex.c | 14 ++++++++------ > 1 files changed, 8 insertions(+), 6 deletions(-) > > diff --git a/kernel/futex.c b/kernel/futex.c > index a6cec32..b217972 100644 > --- a/kernel/futex.c > +++ b/kernel/futex.c > @@ -114,7 +114,7 @@ struct futex_q { > struct plist_node list; > > struct task_struct *task; > - spinlock_t *lock_ptr; > + raw_spinlock_t *lock_ptr; How is this related to the changelog ? Thanks, tglx -- 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/