From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751523AbdFFXq1 (ORCPT ); Tue, 6 Jun 2017 19:46:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32788 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751449AbdFFXqZ (ORCPT ); Tue, 6 Jun 2017 19:46:25 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com BC3ED4E35B Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=pbonzini@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com BC3ED4E35B Date: Tue, 6 Jun 2017 19:46:24 -0400 (EDT) From: Paolo Bonzini To: Andy Lutomirski Cc: Richard Weinberger , linux-x86 64 , linux-kernel@vger.kernel.org, Thomas Meyer Message-ID: <493924181.6519852.1496792784078.JavaMail.zimbra@redhat.com> In-Reply-To: References: <60bf06b3-b72a-6cdc-5743-d547a7c9824f@nod.at> Subject: Re: WARNING: CPU: 0 PID: 1752 at arch/x86/kernel/traps.c:788 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.4.164.1, 10.4.195.3] Thread-Topic: WARNING: CPU: 0 PID: 1752 at arch/x86/kernel/traps.c:788 Thread-Index: 8/4zCTWRhyXtDRxMhBHlVjXxxolUkw== X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 06 Jun 2017 23:46:25 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ----- Original Message ----- > From: "Andy Lutomirski" > To: "Richard Weinberger" , "Paolo Bonzini" > Cc: "Andy Lutomirski" , "linux-x86 64" , linux-kernel@vger.kernel.org, > "Thomas Meyer" > Sent: Wednesday, June 7, 2017 12:46:12 AM > Subject: Re: WARNING: CPU: 0 PID: 1752 at arch/x86/kernel/traps.c:788 > > On Thu, Jun 1, 2017 at 3:46 PM, Richard Weinberger wrote: > > Hi! > > > > UserModeLinux hits the following warning on the host. > > I've extracted the evil ptrace() command sequence, please see attached > > program, > > it triggers the warning too. > > This sounds like a known QEMU bug. Paolo, did this get fixed in QEMU? > If so, what version? If I understood what bug you are referring to, 2.9.0. Commit c52ab08aee ("target-i386: Fix eflags.TF/#DB handling of syscall/sysret insns", 2016-12-22). Paolo