- Kees Cook ha scritto:
> On Mon, Oct 23, 2017 at 7:14 AM, Paolo Bonzini 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.
> >
>
On Mon, Oct 23, 2017 at 7:14 AM, Paolo Bonzini 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
>
On Mon, Oct 23, 2017 at 4:14 PM, Paolo Bonzini 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
>
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"
On Sat, Oct 21, 2017 at 08:06:10PM -0700, Kees Cook wrote:
> On Sat, Oct 21, 2017 at 11:45 AM, Christoffer Dall
> wrote:
> > We do direct useraccess copying to the kvm_cpu_context structure
> > embedded in the kvm_vcpu_arch structure, and to the vcpu debug register
>
On Sat, Oct 21, 2017 at 11:45 AM, Christoffer Dall
wrote:
> We do direct useraccess copying to the kvm_cpu_context structure
> embedded in the kvm_vcpu_arch structure, and to the vcpu debug register
> state. Everything else (timer, PMU, vgic) goes through a temporary