Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754172Ab0AGVq4 (ORCPT ); Thu, 7 Jan 2010 16:46:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754137Ab0AGVqz (ORCPT ); Thu, 7 Jan 2010 16:46:55 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55534 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752871Ab0AGVqy (ORCPT ); Thu, 7 Jan 2010 16:46:54 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Martin Schwidefsky X-Fcc: ~/Mail/linus Cc: Oleg Nesterov , caiqian@redhat.com, Heiko Carstens , Jan Kratochvil , linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, utrace-devel@redhat.com Subject: Re: s390 && user_enable_single_step() (Was: odd utrace testing results on s390x) In-Reply-To: Martin Schwidefsky's message of Thursday, 7 January 2010 10:18:55 +0100 <20100107101855.13248dc2@mschwide.boeblingen.de.ibm.com> References: <20100104155225.GA16650@redhat.com> <20100104171626.22ea2d9c@mschwide.boeblingen.de.ibm.com> <20100104181412.GA21146@redhat.com> <20100104211147.4CC94D532@magilla.sf.frob.com> <20100105105030.66bb8a0a@mschwide.boeblingen.de.ibm.com> <20100105153633.GA9376@redhat.com> <20100105164610.388effd3@mschwide.boeblingen.de.ibm.com> <20100105155913.GA10652@redhat.com> <20100105170301.GA13641@redhat.com> <20100105195818.GA20358@redhat.com> <20100106201722.GB26204@redhat.com> <20100106211329.DB4F5134D@magilla.sf.frob.com> <20100107101855.13248dc2@mschwide.boeblingen.de.ibm.com> X-Antipastobozoticataclysm: Bariumenemanilow Message-Id: <20100107214642.579F27300@magilla.sf.frob.com> Date: Thu, 7 Jan 2010 13:46:42 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 702 Lines: 17 > Clear the TIF_SINGLE_STEP bit in copy_thread. If the new process is > not auto-attached by the tracer it is wrong to delivere SIGTRAP to > the new process. The change is right, but this log entry is confusing. "auto-attached" has nothing to do with it, nor does anything about tracing the new process or not. The new process has not experienced a PER trap of its own, so it is wrong to deliver a SIGTRAP that is meant for its creator. Thanks, Roland -- 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/