WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] [Linux] Transfer TPM locality info in the ringst

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [Linux] Transfer TPM locality info in the ringstructure
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Mon, 7 Jan 2008 06:53:28 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Jan Beulich <jbeulich@xxxxxxxxxx>
Delivery-date: Mon, 07 Jan 2008 03:53:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3A710C6.11CA6%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote on 01/06/2008 06:12:06 PM:

> How does that fix the problem if an old tpm frontend runs against a
> new tpm backend? The unused field will not be initialised by the old
> frontend, hence can contain garbage to confuse the new backend?
>


I don't know of any better solution than initializing this 'now'.

   Stefan


>  -- Keir
>
> On 4/1/08 14:12, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> > >  * Read data from the shared memory and copy it directly into the
> > >  * provided buffer. Advance the read_last indicator which tells
> >
> > Also, while your patch at the first glance appears to take care of backward
> > compatibility, I'm not sure it really does: In the old code, I
> can'tsee where
> > the 'unused' member of 'struct tpmif_tx_request' gets zero-initialized.
>
> Yes, that's a problem. What I'll do is set the 'unused' member to
> zero and leave it at that.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel