linux-kernel - Re: Fix Mes in emulate.c

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>] [day] [month] [year] [list]

Message-ID: <546C6310.305@redhat.com>
Date:	Wed, 19 Nov 2014 10:29:52 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	nick <xerofoify@...il.com>, gleb@...nel.org
CC:	mingo@...hat.com, hpa@...or.com, x86@...nel.org,
	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Fix Mes in emulate.c



On 19/11/2014 04:17, nick wrote:
> Greeting Gleb and other maintainers, I known this may not be that
> easy to fix but if someone is willing to send me the fault addresses
> or a hardware manual in order to fix and add the correct return
> correct addresses for the fix mes in the emulate.c for the x86
> architecture.

Hi Nick,

I need to check more closely, but I think the FIXMEs have already been
fixed.  The address is already stored by arch/x86/kvm/paging_tmpl.h's
FNAME(walk_addr_generic) in walker->fault.address, and propagated by
FNAME(gva_to_gpa).

You can send a patch to remove them.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/