aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing
diff options
context:
space:
mode:
authorJarkko Sakkinen <jarkko.sakkinen@linux.intel.com>2019-02-04 15:59:43 +0200
committerJarkko Sakkinen <jarkko.sakkinen@linux.intel.com>2019-02-08 23:13:02 +0200
commit3d7a850fdc1a2e4d2adbc95cc0fc962974725e88 (patch)
tree0ac237a76bb19c26b560f10264c0d65caded28e2 /tools/testing
parentLSM: SafeSetID: remove unused include (diff)
downloadlinux-dev-3d7a850fdc1a2e4d2adbc95cc0fc962974725e88.tar.xz
linux-dev-3d7a850fdc1a2e4d2adbc95cc0fc962974725e88.zip
tpm/tpm_crb: Avoid unaligned reads in crb_recv()
The current approach to read first 6 bytes from the response and then tail of the response, can cause the 2nd memcpy_fromio() to do an unaligned read (e.g. read 32-bit word from address aligned to a 16-bits), depending on how memcpy_fromio() is implemented. If this happens, the read will fail and the memory controller will fill the read with 1's. This was triggered by 170d13ca3a2f, which should be probably refined to check and react to the address alignment. Before that commit, on x86 memcpy_fromio() turned out to be memcpy(). By a luck GCC has done the right thing (from tpm_crb's perspective) for us so far, but we should not rely on that. Thus, it makes sense to fix this also in tpm_crb, not least because the fix can be then backported to stable kernels and make them more robust when compiled in differing environments. Cc: stable@vger.kernel.org Cc: James Morris <jmorris@namei.org> Cc: Tomas Winkler <tomas.winkler@intel.com> Cc: Jerry Snitselaar <jsnitsel@redhat.com> Fixes: 30fc8d138e91 ("tpm: TPM 2.0 CRB Interface") Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> Reviewed-by: Jerry Snitselaar <jsnitsel@redhat.com> Acked-by: Tomas Winkler <tomas.winkler@intel.com>
Diffstat (limited to 'tools/testing')
0 files changed, 0 insertions, 0 deletions