From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.7] helo=sc8-sf-list1.sourceforge.net) by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43) id 1FmBKz-00086F-Vi for user-mode-linux-devel@lists.sourceforge.net; Fri, 02 Jun 2006 08:13:22 -0700 Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1FmBKz-00052X-Q4 for user-mode-linux-devel@lists.sourceforge.net; Fri, 02 Jun 2006 08:13:21 -0700 Received: from [198.99.130.12] (helo=saraswathi.solana.com) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1FmBKy-0000sX-9D for user-mode-linux-devel@lists.sourceforge.net; Fri, 02 Jun 2006 08:13:21 -0700 Date: Fri, 2 Jun 2006 11:13:35 -0400 From: Jeff Dike Message-ID: <20060602151335.GA4708@ccure.user-mode-linux.org> References: <20060526032424.GA8283@ccure.user-mode-linux.org> <200605261236.26814.ak@suse.de> <20060526141345.GA4152@ccure.user-mode-linux.org> <200606012107.34676.blaisorblade@yahoo.it> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <200606012107.34676.blaisorblade@yahoo.it> Subject: Re: [uml-devel] [discuss] [RFC] [PATCH] Double syscall exit traces on x86_64 List-Id: The user-mode Linux development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: user-mode-linux-devel-bounces@lists.sourceforge.net Errors-To: user-mode-linux-devel-bounces@lists.sourceforge.net To: Blaisorblade Cc: discuss@x86-64.org, Steven James , user-mode-linux-devel@lists.sourceforge.net, Jeff Dike , linux-kernel@vger.kernel.org, Andi Kleen , Roland McGrath On Thu, Jun 01, 2006 at 09:07:33PM +0200, Blaisorblade wrote: > Sorry for the question, but has this been sent to -stable (since it's a > -stable regression, it should be)? To 2.6.17 -git? It's in current git. I'm having a hard time telling when the bug was introduced. The git web interface seems to be telling me that the double notification was around since last year, which I don't believe, since I've run much more recent x86_64 kernels. If the bug existed before 2.6.16, then it's fine -stable fodder. > And have you tested it (somebody should have, but it's not sure)? Yes, it's been continuously and happily running UML since Andi sent me his patch. Jeff _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932212AbWFBPN7 (ORCPT ); Fri, 2 Jun 2006 11:13:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932216AbWFBPN7 (ORCPT ); Fri, 2 Jun 2006 11:13:59 -0400 Received: from saraswathi.solana.com ([198.99.130.12]:33698 "EHLO saraswathi.solana.com") by vger.kernel.org with ESMTP id S932212AbWFBPN6 (ORCPT ); Fri, 2 Jun 2006 11:13:58 -0400 Date: Fri, 2 Jun 2006 11:13:35 -0400 From: Jeff Dike To: Blaisorblade Cc: user-mode-linux-devel@lists.sourceforge.net, discuss@x86-64.org, Steven James , Jeff Dike , Andi Kleen , linux-kernel@vger.kernel.org, Roland McGrath Subject: Re: [uml-devel] [discuss] [RFC] [PATCH] Double syscall exit traces on x86_64 Message-ID: <20060602151335.GA4708@ccure.user-mode-linux.org> References: <20060526032424.GA8283@ccure.user-mode-linux.org> <200605261236.26814.ak@suse.de> <20060526141345.GA4152@ccure.user-mode-linux.org> <200606012107.34676.blaisorblade@yahoo.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200606012107.34676.blaisorblade@yahoo.it> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 01, 2006 at 09:07:33PM +0200, Blaisorblade wrote: > Sorry for the question, but has this been sent to -stable (since it's a > -stable regression, it should be)? To 2.6.17 -git? It's in current git. I'm having a hard time telling when the bug was introduced. The git web interface seems to be telling me that the double notification was around since last year, which I don't believe, since I've run much more recent x86_64 kernels. If the bug existed before 2.6.16, then it's fine -stable fodder. > And have you tested it (somebody should have, but it's not sure)? Yes, it's been continuously and happily running UML since Andi sent me his patch. Jeff