Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754649AbdLOBpc (ORCPT ); Thu, 14 Dec 2017 20:45:32 -0500 Received: from mail-oi0-f65.google.com ([209.85.218.65]:38156 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754538AbdLOBp2 (ORCPT ); Thu, 14 Dec 2017 20:45:28 -0500 X-Google-Smtp-Source: ACJfBouviysg+tYJ63hnP37QEJSZwtvUT+uo09UdJhHBho81hwVR5id9Ekp0wzbkL8+Y7UmRkH938h19Q3aP5Jtm584= MIME-Version: 1.0 In-Reply-To: <20171214141836.7ndd6i3qaef36e2o@starbug-vm.ie.oracle.com> References: <1513259818-11419-1-git-send-email-wanpeng.li@hotmail.com> <20171214141836.7ndd6i3qaef36e2o@starbug-vm.ie.oracle.com> From: Wanpeng Li Date: Fri, 15 Dec 2017 09:45:27 +0800 Message-ID: Subject: Re: [PATCH v3] KVM: X86: Fix stack-out-of-bounds read in write_mmio To: Wanpeng Li , "linux-kernel@vger.kernel.org" , kvm , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Wanpeng Li , Marc Zyngier , Christoffer Dall Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 747 Lines: 22 2017-12-14 22:18 GMT+08:00 Darren Kenny : > Hi, > > I'm wondering about the change to trace_kvm_mmio() here, since it > doesn't appear to be changing the use of it in > virt/kvm/arm/mmio.c, e.g: > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/virt/kvm/arm/mmio.c#n114 > > which seems to be still using it with a data value rather than a > pointer like you've changed it to in the header. > > Should that also be modified to match? As it is, it would appear to > cause a compilation error on ARM (though I've not confirmed). Yeah, fix it in v4, https://lkml.org/lkml/2017/12/14/954 however, I don't have an ARM environment to compile it though the change is very simple. Regards, Wanpeng Li