mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Paolo Bonzini <pbonzini@redhat.com>, Andy Lutomirski <luto@kernel.org>
Cc: linux-x86 64 <linux-x86_64@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Thomas Meyer <thomas@m3y3r.de>
Subject: Re: WARNING: CPU: 0 PID: 1752 at arch/x86/kernel/traps.c:788
Date: Wed, 7 Jun 2017 09:36:15 +0200	[thread overview]
Message-ID: <c77ee750-e3e1-bdb8-64c9-d8507b537c19@nod.at> (raw)
In-Reply-To: <493924181.6519852.1496792784078.JavaMail.zimbra@redhat.com>

Andy, Paolo,

Am 07.06.2017 um 01:46 schrieb Paolo Bonzini:
> 
> 
> ----- Original Message -----
>> From: "Andy Lutomirski" <luto@kernel.org>
>> To: "Richard Weinberger" <richard@nod.at>, "Paolo Bonzini" <pbonzini@redhat.com>
>> Cc: "Andy Lutomirski" <luto@kernel.org>, "linux-x86 64" <linux-x86_64@vger.kernel.org>, linux-kernel@vger.kernel.org,
>> "Thomas Meyer" <thomas@m3y3r.de>
>> 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 <richard@nod.at> 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).

This makes sense. I'll update my qemu and test again.

Thanks,
//richard

      reply	other threads:[~2017-06-07  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 22:46 Richard Weinberger
2017-06-06 22:46 ` Andy Lutomirski
2017-06-06 23:46   ` Paolo Bonzini
2017-06-07  7:36     ` Richard Weinberger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c77ee750-e3e1-bdb8-64c9-d8507b537c19@nod.at \
    --to=richard@nod.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-x86_64@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=thomas@m3y3r.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®