public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-integrity@vger.kernel.org,
	"Jason Gunthorpe" <jgunthorpe@obsidianresearch.com>,
	"Peter Hüwe" <PeterHuewe@gmx.de>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] tpm_i2c_nuvoton: Use common error handling code in i2c_nuvoton_send()
Date: Mon, 23 Oct 2017 15:38:13 +0200	[thread overview]
Message-ID: <20171023133813.3xflw4k2npydp26c@linux.intel.com> (raw)
In-Reply-To: <6d2dcc64-af7a-fb71-f863-10d30914269e@users.sourceforge.net>

On Sat, Oct 21, 2017 at 10:11:36PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Sat, 21 Oct 2017 22:07:39 +0200
> 
> Add a jump target so that a bit of exception handling can be better reused
> at the end of this function.
> 
> This issue was detected by using the Coccinelle software.
> 
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
>  drivers/char/tpm/tpm_i2c_nuvoton.c | 13 +++++++------
>  1 file changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/char/tpm/tpm_i2c_nuvoton.c b/drivers/char/tpm/tpm_i2c_nuvoton.c
> index c6428771841f..f0037e9e2d0e 100644
> --- a/drivers/char/tpm/tpm_i2c_nuvoton.c
> +++ b/drivers/char/tpm/tpm_i2c_nuvoton.c
> @@ -440,15 +440,13 @@ static int i2c_nuvoton_send(struct tpm_chip *chip, u8 *buf, size_t len)
>  	}
>  	if (rc < 0) {
>  		/* retries == TPM_RETRY */
> -		i2c_nuvoton_ready(chip);
> -		return rc;
> +		goto write_ready;
>  	}
>  	/* execute the TPM command */
>  	rc = i2c_nuvoton_write_status(client, TPM_STS_GO);
>  	if (rc < 0) {
>  		dev_err(dev, "%s() fail to write Go\n", __func__);
> -		i2c_nuvoton_ready(chip);
> -		return rc;
> +		goto write_ready;
>  	}
>  	ordinal = be32_to_cpu(*((__be32 *) (buf + 6)));
>  	rc = i2c_nuvoton_wait_for_data_avail(chip,
> @@ -457,12 +455,15 @@ static int i2c_nuvoton_send(struct tpm_chip *chip, u8 *buf, size_t len)
>  					     &priv->read_queue);
>  	if (rc) {
>  		dev_err(dev, "%s() timeout command duration\n", __func__);
> -		i2c_nuvoton_ready(chip);
> -		return rc;
> +		goto write_ready;
>  	}
>  
>  	dev_dbg(dev, "%s() -> %zd\n", __func__, len);
>  	return len;
> +
> +write_ready:
> +	i2c_nuvoton_ready(chip);
> +	return rc;
>  }
>  
>  static bool i2c_nuvoton_req_canceled(struct tpm_chip *chip, u8 status)
> -- 
> 2.14.2
> 

Setting the commandReady bit gives means to abort the command. Setting
the bit is not the end goal. Use something like err_cancel instead.

/Jarkko

  reply	other threads:[~2017-10-23 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21 20:11 [PATCH] tpm_i2c_nuvoton: Use common error handling code in i2c_nuvoton_send() SF Markus Elfring
2017-10-23 13:38 ` Jarkko Sakkinen [this message]
2017-10-23 13:46   ` SF Markus Elfring

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=20171023133813.3xflw4k2npydp26c@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=PeterHuewe@gmx.de \
    --cc=elfring@users.sourceforge.net \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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