All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	linux-integrity@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Peter Huewe <PeterHuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>,
	Alexander Steffen <Alexander.Steffen@infineon.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] tpm: Unify the send callback behaviour
Date: Fri, 8 Feb 2019 11:36:19 -0500	[thread overview]
Message-ID: <22ef544f-e841-a8ea-cec7-fb64fe368fe8@linux.ibm.com> (raw)
In-Reply-To: <20190208163059.640-2-jarkko.sakkinen@linux.intel.com>

On 2/8/19 11:30 AM, Jarkko Sakkinen wrote:
>   static void tpm_nsc_cancel(struct tpm_chip *chip)
> diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c
> index 60e2038652b8..1d781c19f112 100644
> --- a/drivers/char/tpm/tpm_tis_core.c
> +++ b/drivers/char/tpm/tpm_tis_core.c
> @@ -507,7 +507,11 @@ static int tpm_tis_send(struct tpm_chip *chip, u8 *buf, size_t len)
>   	if (!priv->irq_tested)
>   		disable_interrupts(chip);
>   	priv->irq_tested = true;
> -	return rc;
> +
> +	if (rc < 0)
> +		return rc;
> +
> +	return 0;
>   }


That's not all... There's this above it as well with tpm_tis_send_main 
returning with 'return len;'.

     if (!(chip->flags & TPM_CHIP_FLAG_IRQ) || priv->irq_tested)
         return tpm_tis_send_main(chip, buf, len);



  reply	other threads:[~2019-02-08 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 16:30 [PATCH v3 0/2] tpm: Unify send() callbacks Jarkko Sakkinen
2019-02-08 16:30 ` [PATCH v3 1/2] tpm: Unify the send callback behaviour Jarkko Sakkinen
2019-02-08 16:36   ` Stefan Berger [this message]
2019-02-08 17:59     ` Jarkko Sakkinen
2019-02-08 16:54   ` Stefan Berger
2019-02-08 16:30 ` [PATCH v3 2/2] tpm/tpm_i2c_atmel: Return -E2BIG when the transfer is incomplete Jarkko Sakkinen
2019-02-08 16:48   ` Stefan Berger

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=22ef544f-e841-a8ea-cec7-fb64fe368fe8@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=Alexander.Steffen@infineon.com \
    --cc=PeterHuewe@gmx.de \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --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 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.