From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752547AbcHIIOP (ORCPT ); Tue, 9 Aug 2016 04:14:15 -0400 Received: from mga03.intel.com ([134.134.136.65]:22479 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751654AbcHIIOM (ORCPT ); Tue, 9 Aug 2016 04:14:12 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,493,1464678000"; d="scan'208";a="1011022079" Date: Tue, 9 Aug 2016 11:14:02 +0300 From: Jarkko Sakkinen To: Andrey Pronin Cc: Peter Huewe , Marcel Selhorst , Jason Gunthorpe , tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Christophe Ricard , dtor@chromium.org, smbarber@chromium.org, dianders@chromium.org Subject: Re: [PATCH v3 1/2] tpm_tis_core: add optional max xfer size check Message-ID: <20160809081402.GA10537@intel.com> References: <1468546745-14646-1-git-send-email-apronin@chromium.org> <1469677797-74304-2-git-send-email-apronin@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1469677797-74304-2-git-send-email-apronin@chromium.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 27, 2016 at 08:49:56PM -0700, Andrey Pronin wrote: > If tpm reports a bigger burstcnt than allowed by the physical protocol, > set burstcnt to the max allowed value. > > In practice, seen in case of xfer issues (e.g. in spi interface case, > lost header causing flow control issues and wrong values returned on read > from TPM_STS). Without catching, causes the physical layer to reject xfer. > > Signed-off-by: Andrey Pronin Reviewed-by: Jarkko Sakkinen I don't have hardware to test this. Someone should validate that it does not break anything. Christophe, are you able to do this? /Jarkko > --- > drivers/char/tpm/tpm_tis_core.c | 9 ++++++++- > drivers/char/tpm/tpm_tis_core.h | 1 + > 2 files changed, 9 insertions(+), 1 deletion(-) > > diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c > index f22caf8..7c4fa0c 100644 > --- a/drivers/char/tpm/tpm_tis_core.c > +++ b/drivers/char/tpm/tpm_tis_core.c > @@ -168,8 +168,15 @@ static int get_burstcount(struct tpm_chip *chip) > return rc; > > burstcnt = (value >> 8) & 0xFFFF; > - if (burstcnt) > + if (burstcnt) { > + if (priv->phy_ops->max_xfer_size && > + (burstcnt > priv->phy_ops->max_xfer_size)) { > + dev_warn(&chip->dev, > + "Bad burstcnt read: %d\n", burstcnt); > + burstcnt = priv->phy_ops->max_xfer_size; > + } > return burstcnt; > + } > msleep(TPM_TIMEOUT); > } while (time_before(jiffies, stop)); > return -EBUSY; > diff --git a/drivers/char/tpm/tpm_tis_core.h b/drivers/char/tpm/tpm_tis_core.h > index 9191aab..58e8b14 100644 > --- a/drivers/char/tpm/tpm_tis_core.h > +++ b/drivers/char/tpm/tpm_tis_core.h > @@ -102,6 +102,7 @@ struct tpm_tis_phy_ops { > int (*read16)(struct tpm_tis_data *data, u32 addr, u16 *result); > int (*read32)(struct tpm_tis_data *data, u32 addr, u32 *result); > int (*write32)(struct tpm_tis_data *data, u32 addr, u32 src); > + u16 max_xfer_size; > }; > > static inline int tpm_tis_read_bytes(struct tpm_tis_data *data, u32 addr, > -- > 2.6.6 > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Sakkinen Subject: Re: [PATCH v3 1/2] tpm_tis_core: add optional max xfer size check Date: Tue, 9 Aug 2016 11:14:02 +0300 Message-ID: <20160809081402.GA10537@intel.com> References: <1468546745-14646-1-git-send-email-apronin@chromium.org> <1469677797-74304-2-git-send-email-apronin@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1469677797-74304-2-git-send-email-apronin-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tpmdd-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Andrey Pronin Cc: Christophe Ricard , dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, smbarber-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, dtor-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org List-Id: tpmdd-devel@lists.sourceforge.net On Wed, Jul 27, 2016 at 08:49:56PM -0700, Andrey Pronin wrote: > If tpm reports a bigger burstcnt than allowed by the physical protocol, > set burstcnt to the max allowed value. > > In practice, seen in case of xfer issues (e.g. in spi interface case, > lost header causing flow control issues and wrong values returned on read > from TPM_STS). Without catching, causes the physical layer to reject xfer. > > Signed-off-by: Andrey Pronin Reviewed-by: Jarkko Sakkinen I don't have hardware to test this. Someone should validate that it does not break anything. Christophe, are you able to do this? /Jarkko > --- > drivers/char/tpm/tpm_tis_core.c | 9 ++++++++- > drivers/char/tpm/tpm_tis_core.h | 1 + > 2 files changed, 9 insertions(+), 1 deletion(-) > > diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c > index f22caf8..7c4fa0c 100644 > --- a/drivers/char/tpm/tpm_tis_core.c > +++ b/drivers/char/tpm/tpm_tis_core.c > @@ -168,8 +168,15 @@ static int get_burstcount(struct tpm_chip *chip) > return rc; > > burstcnt = (value >> 8) & 0xFFFF; > - if (burstcnt) > + if (burstcnt) { > + if (priv->phy_ops->max_xfer_size && > + (burstcnt > priv->phy_ops->max_xfer_size)) { > + dev_warn(&chip->dev, > + "Bad burstcnt read: %d\n", burstcnt); > + burstcnt = priv->phy_ops->max_xfer_size; > + } > return burstcnt; > + } > msleep(TPM_TIMEOUT); > } while (time_before(jiffies, stop)); > return -EBUSY; > diff --git a/drivers/char/tpm/tpm_tis_core.h b/drivers/char/tpm/tpm_tis_core.h > index 9191aab..58e8b14 100644 > --- a/drivers/char/tpm/tpm_tis_core.h > +++ b/drivers/char/tpm/tpm_tis_core.h > @@ -102,6 +102,7 @@ struct tpm_tis_phy_ops { > int (*read16)(struct tpm_tis_data *data, u32 addr, u16 *result); > int (*read32)(struct tpm_tis_data *data, u32 addr, u32 *result); > int (*write32)(struct tpm_tis_data *data, u32 addr, u32 src); > + u16 max_xfer_size; > }; > > static inline int tpm_tis_read_bytes(struct tpm_tis_data *data, u32 addr, > -- > 2.6.6 > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev