linux-kernel - Re: WARNING: CPU: 0 PID: 1752 at arch/x86/kernel/traps.c:788

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c77ee750-e3e1-bdb8-64c9-d8507b537c19@nod.at>
Date:   Wed, 7 Jun 2017 09:36:15 +0200
From:   Richard Weinberger <richard@....at>
To:     Paolo Bonzini <pbonzini@...hat.com>,
        Andy Lutomirski <luto@...nel.org>
Cc:     linux-x86 64 <linux-x86_64@...r.kernel.org>,
        linux-kernel@...r.kernel.org, Thomas Meyer <thomas@...3r.de>
Subject: Re: WARNING: CPU: 0 PID: 1752 at arch/x86/kernel/traps.c:788

Andy, Paolo,

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