All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: stable@vger.kernel.org, James Morris <jmorris@namei.org>,
	Tomas Winkler <tomas.winkler@intel.com>,
	Jerry Snitselaar <jsnitsel@redhat.com>
Subject: Re: [PATCH] tpm/tpm_crb: Avoid unaligned reads in crb_recv()
Date: Mon, 15 Apr 2019 12:48:25 +0200	[thread overview]
Message-ID: <20190415104824.GB9397@kroah.com> (raw)
In-Reply-To: <20190410135432.28684-1-jarkko.sakkinen@linux.intel.com>

On Wed, Apr 10, 2019 at 04:54:32PM +0300, Jarkko Sakkinen wrote:
> commit 3d7a850fdc1a2e4d2adbc95cc0fc962974725e88 upstream
> 
> 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>
> ---
> backport v4.4.178
>  drivers/char/tpm/tpm_crb.c | 22 ++++++++++++++++------
>  1 file changed, 16 insertions(+), 6 deletions(-)

I need a 4.9.y version first before I can take a 4.4.y version, as we do
not want anyone to have a regression moving from 4.4.y to a newer
kernel.

thanks,

greg k-h

  reply	other threads:[~2019-04-15 10:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 13:54 [PATCH] tpm/tpm_crb: Avoid unaligned reads in crb_recv() Jarkko Sakkinen
2019-04-15 10:48 ` Greg KH [this message]
2019-04-16  7:25   ` Jarkko Sakkinen
  -- strict thread matches above, loose matches on Subject: below --
2019-04-17 14:59 Jarkko Sakkinen
2019-04-17 15:42 ` Sasha Levin
2019-02-01 11:19 [PATCH] tpm/tpm_crb: Avoid unaligned reads in crb_recv(): Jarkko Sakkinen
2019-02-01 17:49 ` Linus Torvalds
2019-02-04 11:47   ` Jarkko Sakkinen
2019-02-01 18:42 ` Jerry Snitselaar
2019-02-01 19:20 ` Winkler, Tomas
2019-02-04 11:44   ` Jarkko Sakkinen
2019-02-04 12:17 ` David Laight
2019-02-05 10:44   ` Jarkko Sakkinen
2019-02-05 10:47     ` Jarkko Sakkinen
2019-02-05 10:49       ` Jarkko Sakkinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190415104824.GB9397@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jmorris@namei.org \
    --cc=jsnitsel@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tomas.winkler@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.