Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751047AbaBWFZJ (ORCPT ); Sun, 23 Feb 2014 00:25:09 -0500 Received: from terminus.zytor.com ([198.137.202.10]:46848 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750780AbaBWFZI (ORCPT ); Sun, 23 Feb 2014 00:25:08 -0500 User-Agent: K-9 Mail for Android In-Reply-To: References: <53084317.4090304@zytor.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: perf_fuzzer compiled for x32 causes reboot From: "H. Peter Anvin" Date: Sat, 22 Feb 2014 21:24:11 -0800 To: Vince Weaver CC: Linux Kernel , Peter Zijlstra , Ingo Molnar , "H.J. Lu" Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org What is the instructions around it, by any chance? On February 22, 2014 9:18:17 PM PST, Vince Weaver wrote: >On Fri, 21 Feb 2014, H. Peter Anvin wrote: > >> Error 6 reflects a write in userspace to a not-present page. >> >> Since your previous trace indicates that the value of the register in >question >> is a different one, I'm guessing that what we have here is PEBS >getting >> activated. 0x120 is 2*0x90, and 0x90 is the size of a 64-bit PEBS >record. > >I'm having problems generating a replayable syscall trace that exhibits > >the problem. > >It turns out that the segfault address listed (the multiple of 0x120) >happens to be the value in the RBP register at the time of the >segfault. > >That's odd, as the instruction is > movdqa %xmm0,(%rdi) >and rdi is the valid mmap address of the perf ring buffer > rdi 0xf7768000 4151738368 > >so I'm not sure why RBP is involved at all. > >In all of the cases I've investigated the precise_ip value has been set > >for the problem event... but none of the events have been hardware >events >(software and breakpoint so far). So probably not PEBS related? > >Vince -- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- 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/