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] Re: Getting rid of xenbus_suspend(): tpmfront driverimpa

To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: Getting rid of xenbus_suspend(): tpmfront driverimpacted?
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Sun, 5 Nov 2006 12:45:39 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 05 Nov 2006 09:46:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <8A87A9A84C201449A0C56B728ACF491E01F720@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote on 11/05/2006 11:44:14 AM:

> The TPM protocol in contrast assumes a
> > reliable connection from the computer to the device and that all
> commands
> > finish correctly and responses are received by the apps *and* that
> requests
> > are not resent. How does the block driver handle this? Will the
> frontend
> > driver still receive explicit notification of a shutdown?
>
> Blkfront remembers un-acknowledged requests and reissues them after a
> re-connect. It doesn't matter whether the requests have previously been


I  cannot possibly reissue commands like a TPM_Extend(value). It's performing a hashing operation on a register of the TPM using a formular like

PCR_n = SHA1(PCR_n || value)

where || is a concatenation of two byte arrays.

So issuing this command twice would put the TPM's PCR register into a state that it is not supposed to be in.

> issued or not, as we know there will be no reordering hazards within the
> request stream, as there are no ordering guarantees. It currently
> doesn't use the suspend notification.


Unfortunately the TPM is a device with different constraints.

  Stefan

PS: Specs for the TPM are here:
https://www.trustedcomputinggroup.org/specs/TPM/tpmwg-mainrev62_Part3_Commands.pdf
page 114 talks about the TPM_Extend command.


>
> Ian
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel