Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758000AbYGJXDg (ORCPT ); Thu, 10 Jul 2008 19:03:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753927AbYGJXD2 (ORCPT ); Thu, 10 Jul 2008 19:03:28 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:34173 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753260AbYGJXD1 (ORCPT ); Thu, 10 Jul 2008 19:03:27 -0400 Date: Thu, 10 Jul 2008 16:02:47 -0700 (PDT) From: Linus Torvalds To: Roland McGrath cc: Ingo Molnar , Thomas Gleixner , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86_64: fix delayed signals In-Reply-To: Message-ID: References: <20080710215039.2A143154218@magilla.localdomain> <20080710224256.AD038154218@magilla.localdomain> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) 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: 651 Lines: 17 On Thu, 10 Jul 2008, Linus Torvalds wrote: > > You're ignoring the background question - we expressly _stopped_ doing > this long ago. So the real issue was the ".. if you really .." part. Side note: the fact that 32-bit does it seems to imply it's ok, but it bothers me that I know we changed the signal code at some point. Is the 64-bit code doing the exact _same_ things as 32-bit now? Linus -- 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/