From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
Stefan Berger <stefanb@linux.ibm.com>,
Jerry Snitselaar <jsnitsel@redhat.com>
Subject: Re: [PATCH for-4.14] tpm: Unify the mismatching TPM space buffer sizes
Date: Fri, 4 Sep 2020 15:05:29 +0300 [thread overview]
Message-ID: <20200904120529.GD39023@linux.intel.com> (raw)
In-Reply-To: <20200831185849.2696852-1-stefanb@linux.vnet.ibm.com>
On Mon, Aug 31, 2020 at 02:58:49PM -0400, Stefan Berger wrote:
> From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
> The size of the buffers for storing context's and sessions can vary from
> arch to arch as PAGE_SIZE can be anything between 4 kB and 256 kB (the
> maximum for PPC64). Define a fixed buffer size set to 16 kB. This should be
> enough for most use with three handles (that is how many we allow at the
> moment). Parametrize the buffer size while doing this, so that it is easier
> to revisit this later on if required.
>
> Cc: stable@vger.kernel.org
> Reported-by: Stefan Berger <stefanb@linux.ibm.com>
> Fixes: 745b361e989a ("tpm: infrastructure for TPM spaces")
> Reviewed-by: Jerry Snitselaar <jsnitsel@redhat.com>
> Tested-by: Stefan Berger <stefanb@linux.ibm.com>
> Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Thank you for doing this.
You are missing one thing from this.
You need to have this line before the long description:
"commit <original commit ID> upstream"
It is documented over here:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
/Jarkko
next prev parent reply other threads:[~2020-09-04 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 18:58 [PATCH for-4.14] tpm: Unify the mismatching TPM space buffer sizes Stefan Berger
2020-09-04 12:05 ` Jarkko Sakkinen [this message]
2020-09-04 12:21 ` Greg KH
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=20200904120529.GD39023@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jsnitsel@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
--cc=stefanb@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox