From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "Hon Ching(Vicky) Lo" <honclo@linux.vnet.ibm.com>
Cc: tpmdd-devel@lists.sourceforge.net,
Peter Huewe <PeterHuewe@gmx.de>,
Ashley Lai <ashley@ashleylai.com>,
Vicky Lo <honclo2014@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vTPM: fix missing error handling for suspend operation
Date: Fri, 4 Mar 2016 18:55:38 +0200 [thread overview]
Message-ID: <20160304165537.GA13204@intel.com> (raw)
In-Reply-To: <1456899827-14365-1-git-send-email-honclo@linux.vnet.ibm.com>
On Wed, Mar 02, 2016 at 01:23:47AM -0500, Hon Ching(Vicky) Lo wrote:
> ibmvtpm_send_crq in tpm_ibmvtpm_suspend returns errors in a more
> granular level than what the existing code does. This patch adds
> the missing CRQ transport event code checks to ensure appropriate
> action taken, in the case that ibmvtpm_send_crq returns H_CLOSED.
>
> Signed-off-by: Hon Ching(Vicky) Lo <honclo@linux.vnet.ibm.com>
> ---
> drivers/char/tpm/tpm_ibmvtpm.c | 58 +++++++++++++++++++++++++++++++++++++---
> drivers/char/tpm/tpm_ibmvtpm.h | 9 ++++++
> 2 files changed, 63 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/char/tpm/tpm_ibmvtpm.c b/drivers/char/tpm/tpm_ibmvtpm.c
> index 3e6a226..5d984af 100644
> --- a/drivers/char/tpm/tpm_ibmvtpm.c
> +++ b/drivers/char/tpm/tpm_ibmvtpm.c
> @@ -335,17 +335,61 @@ static int tpm_ibmvtpm_suspend(struct device *dev)
> struct ibmvtpm_crq crq;
> u64 *buf = (u64 *) &crq;
> int rc = 0;
> + int sig;
>
> - crq.valid = (u8)IBMVTPM_VALID_CMD;
> - crq.msg = (u8)VTPM_PREPARE_TO_SUSPEND;
> + crq_initialized = 0;
> + crq.valid = (u8) IBMVTPM_VALID_CMD;
> + crq.msg = (u8) VTPM_PREPARE_TO_SUSPEND;
>
> rc = ibmvtpm_send_crq(ibmvtpm->vdev, cpu_to_be64(buf[0]),
> cpu_to_be64(buf[1]));
> +
> + if ((rc == H_CLOSED) && (crq.valid == (u8) VALID_TRANSPORT_EVENT)) {
What if rc == H_CLOSED and crq.valid != VALID_TRANSPORT_EVENT?
> + if (crq.msg == (u8) PARTNER_PARTITION_SUSPENDED) {
> + /* The "partner partition suspended" transport
> + * event disables the associated CRQ such that
> + * any H_SEND_CRQ hcall() to the associated CRQ
> + * returns H_Closed until CRQ has been explicitly
> + * enabled using the H_ENABLED_CRQ hcall.
> + */
> + return H_SUCCESS;
I'm having trouble to understand when the suspend happens through this
route and when you just get H_SUCCESS from ibmvtpm_send_crq(). It
seems that there are two ways how suspend can happen.
I don't understand the big picture.
> + } else if (crq.msg == (u8) PARTNER_PARTITION_FAILED) {
> + dev_err(ibmvtpm->dev,
> + "vtpm has terminated fatally; reboot to reinstate a trusted state.\n");
> + } else if (crq.msg == (u8) PARTNER_PARTITION_DEREG_CRQ) {
> + /* The vtpm is in the process of being reloaded by
> + * firmware and has de-registered CRQ. The client
> + * must wait for the CRQ INITIALIZATION message and
> + * respond and must resubmit suspend message.
> + */
> + sig =
> + wait_event_interruptible(ibmvtpm->wq,
> + crq_initialized == 1);
> + if (sig)
> + return -EINTR;
> +
> + if (suspend_again_count < 1) {
> + suspend_again_count++;
> + goto suspendagain;
> + }
> + } else
> + ;
> + }
> +
> if (rc != H_SUCCESS)
> - dev_err(ibmvtpm->dev,
> - "tpm_ibmvtpm_suspend failed rc=%d\n", rc);
> + dev_err(ibmvtpm->dev, "tpm_ibmvtpm_suspend failed rc=%d\n", rc);
>
> return rc;
> +
> +suspendagain:
> + rc = tpm_ibmvtpm_suspend(ibmvtpm->dev);
> + suspend_again_count = 0;
> +
> + if (rc != H_SUCCESS)
> + dev_err(ibmvtpm->dev, "tpm_ibmvtpm_suspend failed rc=%d\n", rc);
> +
> + return rc;
> +
Get rid of this horrible looking tail recursion thing.
What the heck is suspend_again_count and why it can be module scope
variable? You could use a local variable instead if you would iterate
with a loop.
/Jarkko
next prev parent reply other threads:[~2016-03-04 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 6:23 [PATCH] vTPM: fix missing error handling for suspend operation Hon Ching(Vicky) Lo
2016-03-02 6:23 ` Hon Ching(Vicky) Lo
2016-03-04 16:55 ` Jarkko Sakkinen [this message]
[not found] ` <20160304165537.GA13204-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-03-08 20:44 ` Hon Ching(Vicky) Lo
2016-03-08 20:44 ` Hon Ching(Vicky) Lo
[not found] ` <1457469855.30806.14.camel-0wQ8x0XRVuT1ENwx4SLHqw@public.gmane.org>
2016-03-08 22:54 ` Hon Ching(Vicky) Lo
2016-03-08 22:54 ` Hon Ching(Vicky) Lo
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=20160304165537.GA13204@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=PeterHuewe@gmx.de \
--cc=ashley@ashleylai.com \
--cc=honclo2014@gmail.com \
--cc=honclo@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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.