Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754391Ab3HESvx (ORCPT ); Mon, 5 Aug 2013 14:51:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40973 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754305Ab3HESvu (ORCPT ); Mon, 5 Aug 2013 14:51:50 -0400 Date: Mon, 5 Aug 2013 20:46:25 +0200 From: Oleg Nesterov To: Felipe Contreras Cc: Linus Torvalds , Linux Kernel Mailing List Subject: Re: Linux 3.11-rc4 Message-ID: <20130805184625.GA11633@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 895 Lines: 25 On 08/04, Felipe Contreras wrote: > > I found a regression while running all v3.11-rcX kernels; Starcract II > through wine crashes. The culprit is fab840f (ptrace: PTRACE_DETACH > should do flush_ptrace_hw_breakpoint(child)), I revert that commit and > there's no crash. Heh. I pulled wine-git. set_thread_context() does a lot of PTRACE_POKEUSER requests and then it calls resume_after_ptrace() which simply does PTRACE_DETACH. I'll recheck tomorrow, but it really looks as if it _wants_ to leak the debug registers after detach. And more, it does PTRACE_ATTACH only to set these regs. And this is exactly what fab840f tries to prevent. Oleg. -- 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/