Re: [PATCH v2 0/2] tpm: add optional max xfer size check

2016-07-20 Thread Jarkko Sakkinen
On Tue, Jul 19, 2016 at 07:34:18PM -0700, Andrey Pronin wrote: > This patchset introduces an optional maximum transfer size that can > be specified by a tpm driver. Setting the max_xfer_size helps to catch > the cases when burstcnt is incorrectly reported by the device (e.g. >64 > for spi -

Re: [PATCH v2 0/2] tpm: add optional max xfer size check

2016-07-20 Thread Jarkko Sakkinen
On Tue, Jul 19, 2016 at 07:34:18PM -0700, Andrey Pronin wrote: > This patchset introduces an optional maximum transfer size that can > be specified by a tpm driver. Setting the max_xfer_size helps to catch > the cases when burstcnt is incorrectly reported by the device (e.g. >64 > for spi -

[PATCH v2 0/2] tpm: add optional max xfer size check

2016-07-19 Thread Andrey Pronin
This patchset introduces an optional maximum transfer size that can be specified by a tpm driver. Setting the max_xfer_size helps to catch the cases when burstcnt is incorrectly reported by the device (e.g. >64 for spi - happened in practice) and gracefully handle such situations. v2: removed

[PATCH v2 0/2] tpm: add optional max xfer size check

2016-07-19 Thread Andrey Pronin
This patchset introduces an optional maximum transfer size that can be specified by a tpm driver. Setting the max_xfer_size helps to catch the cases when burstcnt is incorrectly reported by the device (e.g. >64 for spi - happened in practice) and gracefully handle such situations. v2: removed