Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755487AbYKOKAk (ORCPT ); Sat, 15 Nov 2008 05:00:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753346AbYKOKAb (ORCPT ); Sat, 15 Nov 2008 05:00:31 -0500 Received: from fk-out-0910.google.com ([209.85.128.189]:50483 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753015AbYKOKAa (ORCPT ); Sat, 15 Nov 2008 05:00:30 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:to:cc:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding:from; b=bezQqk0IGzrNK5jUgbwY6I8wzgglZUOjfPeorH+zPbu4xosAzvZ4KcEydMLTPoESnO xHamNKMvHWgTLVRRCoJqtsdTwHe0dGbS3sanWFmSEPWiZUVjdkgZNYagvcV8UHYlxCGP Y3Son9uEgg9CkgGhNzhUz5JoXztrUJ/V9CXNo= Subject: [patch] x86, bts: fix unlock problem in ds.c To: lkml Cc: work , "H. Peter Anvin" , stephane eranian , Thomas Gleixner , Ingo Molnar Content-Type: text/plain Date: Sat, 15 Nov 2008 11:00:17 +0100 Message-Id: <1226743217.6162.4.camel@raistlin> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit From: Markus Metzger Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 869 Lines: 29 Fix a problem where ds_request() returned an error without releasing the ds lock. Reported-by: Stephane Eranian Signed-off-by: Markus Metzger --- Index: gits/arch/x86/kernel/ds.c =================================================================== --- gits.orig/arch/x86/kernel/ds.c 2008-11-15 10:51:51.000000000 +0100 +++ gits/arch/x86/kernel/ds.c 2008-11-15 10:53:43.000000000 +0100 @@ -384,8 +384,9 @@ spin_lock(&ds_lock); + error = -EPERM; if (!check_tracer(task)) - return -EPERM; + goto out_unlock; error = -ENOMEM; context = ds_alloc_context(task); -- 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/