From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
stable@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] [PATCH] tpm: fix rollback when adding char dev fails
Date: Tue, 2 Feb 2016 16:17:35 -0700 [thread overview]
Message-ID: <20160202231735.GB32711@obsidianresearch.com> (raw)
In-Reply-To: <1454113694-7997-1-git-send-email-jarkko.sakkinen@linux.intel.com>
On Fri, Jan 29, 2016 at 04:28:14PM -0800, Jarkko Sakkinen wrote:
> Fixed rollback and gave better names to the functions (more
> self-documenting, less confusing).
>
> Fixes: d972b0523f ("tpm: fix call order in tpm-chip.c")
> Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> cc: stable@vger.kernel.org
> drivers/char/tpm/tpm-chip.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/char/tpm/tpm-chip.c b/drivers/char/tpm/tpm-chip.c
> index 45cc39a..1a9dcee 100644
> +++ b/drivers/char/tpm/tpm-chip.c
> @@ -140,7 +140,7 @@ struct tpm_chip *tpmm_chip_alloc(struct device *dev,
> }
> EXPORT_SYMBOL_GPL(tpmm_chip_alloc);
>
> -static int tpm_dev_add_device(struct tpm_chip *chip)
> +static int tpm_add_char_device(struct tpm_chip *chip)
> {
> int rc;
>
> @@ -151,7 +151,6 @@ static int tpm_dev_add_device(struct tpm_chip *chip)
> chip->devname, MAJOR(chip->dev.devt),
> MINOR(chip->dev.devt), rc);
>
> - device_unregister(&chip->dev);
> return rc;
> }
> @@ -162,13 +161,14 @@ static int tpm_dev_add_device(struct tpm_chip *chip)
> chip->devname, MAJOR(chip->dev.devt),
> MINOR(chip->dev.devt), rc);
>
> + cdev_del(&chip->cdev);
> return rc;
Yep.
Reviewed-By: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Jason
prev parent reply other threads:[~2016-02-02 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 0:28 Jarkko Sakkinen
2016-02-02 23:17 ` Jason Gunthorpe [this message]
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=20160202231735.GB32711@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®