From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] x86/EFI: permit setting variable with non-zero attributes Date: Tue, 26 Mar 2013 17:20:26 +0000 Message-ID: References: <5151E1D102000078000C8AC0@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5151E1D102000078000C8AC0@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , xen-devel List-Id: xen-devel@lists.xenproject.org On 26/03/2013 16:58, "Jan Beulich" wrote: > This must have been a copy-and-paste mistake - get_variable uses > op->misc as output only, and wants to make sure it's zero for future > extensibility. For set_variable, this is an input though, and hence > the check is wrong. > > Signed-off-by: Jan Beulich Acked-by: Keir Fraser > --- a/xen/arch/x86/efi/runtime.c > +++ b/xen/arch/x86/efi/runtime.c > @@ -398,9 +398,6 @@ int efi_runtime_call(struct xenpf_efi_ru > long len; > unsigned char *data; > > - if ( op->misc ) > - return -EINVAL; > - > len = gwstrlen(guest_handle_cast(op->u.set_variable.name, CHAR16)); > if ( len < 0 ) > return len; > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel