[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1024881182.14288556.1508792774084.JavaMail.zimbra@redhat.com>
Date: Mon, 23 Oct 2017 17:06:14 -0400 (EDT)
From: Paolo Bonzini <pbonzini@...hat.com>
To: Kees Cook <keescook@...omium.org>
Cc: Christoffer Dall <cdall@...aro.org>,
Christoffer Dall <christoffer.dall@...aro.org>,
kvmarm@...ts.cs.columbia.edu, linux-arm-kernel@...ts.infradead.org,
KVM <kvm@...r.kernel.org>, kernel-hardening@...ts.openwall.com,
Radim Krčmář <rkrcmar@...hat.com>,
Marc Zyngier <marc.zyngier@....com>
Subject: R: Re: [PATCH] KVM: arm/arm64: Allow usercopy to vcpu->arch.ctxt
and arm64 debug
----- Kees Cook <keescook@...omium.org> ha scritto:
> On Mon, Oct 23, 2017 at 7:14 AM, Paolo Bonzini <pbonzini@...hat.com> wrote:
> > On 22/10/2017 09:44, Christoffer Dall wrote:
> >> However, I think it's much clearer if I
> >> rewrite these to use get_user() and put_user(). v2 incoming.
> >
> > I'd actually prefer if you all do a trivial conversion to
> > kvm_init_usercopy to begin with. In fact, we could just change the
> > default from "0, 0" to "0, sizeof (kvm_arch_vcpu)" in kvm_init. Any
> > other change can be applied after the patches are merged to Linus's
> > tree, especially with KVM Forum and the merge window both coming soon.
> >
> > I'll send a v2 myself later this week.
>
> Okay, which patches would you like me to carry in the usercopy
> whitelisting tree for the coming merge window?
v2 of mine, which shall come in the next couple of days.
Paolo
>
> -Kees
>
> --
> Kees Cook
> Pixel Security
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
