From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e28smtp06.in.ibm.com (e28smtp06.in.ibm.com [122.248.162.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e28smtp06.in.ibm.com", Issuer "GeoTrust SSL CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 9C3D6B70D6 for ; Sun, 2 Jan 2011 23:54:09 +1100 (EST) Received: from d28relay05.in.ibm.com (d28relay05.in.ibm.com [9.184.220.62]) by e28smtp06.in.ibm.com (8.14.4/8.13.1) with ESMTP id p02Cs5Wn031089 for ; Sun, 2 Jan 2011 18:24:05 +0530 Received: from d28av01.in.ibm.com (d28av01.in.ibm.com [9.184.220.63]) by d28relay05.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p02Cs4Ae2949360 for ; Sun, 2 Jan 2011 18:24:04 +0530 Received: from d28av01.in.ibm.com (loopback [127.0.0.1]) by d28av01.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p02Cs33m019525 for ; Sun, 2 Jan 2011 18:24:04 +0530 Date: Sun, 2 Jan 2011 18:24:01 +0530 From: "K.Prasad" To: Andreas Schwab Subject: Re: ppc_set_hwdebug vs ptrace_set_debugreg Message-ID: <20110102125401.GA2390@in.ibm.com> References: <20101129072233.GA15560@in.ibm.com> <20101201043758.GA2219@in.ibm.com> <20101213082619.GA6582@in.ibm.com> <20101214125427.GA2443@in.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: linuxppc-dev@ozlabs.org, Dave Kleikamp , Srikar Dronamraju , Paul Mackerras Reply-To: prasad@linux.vnet.ibm.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Dec 16, 2010 at 06:07:47PM +0100, Andreas Schwab wrote: > "K.Prasad" writes: > > > How about the revised patch below? It is only compile-tested; have you > > got a quick test case that I can run? > > It crashes the kernel when running the watch-vfork test. > > Andreas. > Hi Andreas, I tried running it multiple times but saw no crash (or error messages in dmesg). Can you send me the crash logs? What's the behaviour when the testcase is run on an unpatched kernel? The watch-vfork test actually fails on my system (4 unexpected failures) irrespective of the kernel containing the patch or not. Thanks, K.Prasad P.S.: I'd been on vacation and couldn't look at this issue during then.