linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	"tpmdd-devel@lists.sourceforge.net" 
	<tpmdd-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tpm: don't destroy chip device prematurely
Date: Tue, 4 Oct 2016 08:19:46 +0300	[thread overview]
Message-ID: <20161004051946.GA10572@intel.com> (raw)
In-Reply-To: <20161003124836.GE9990@intel.com>

On Mon, Oct 03, 2016 at 03:48:36PM +0300, Jarkko Sakkinen wrote:
> On Mon, Oct 03, 2016 at 07:05:48AM +0000, Winkler, Tomas wrote:
> > 
> > > On Sun, Oct 02, 2016 at 01:24:55PM +0300, Jarkko Sakkinen wrote:
> > > > On Sun, Oct 02, 2016 at 01:17:55PM +0300, Jarkko Sakkinen wrote:
> > > > > On Sun, Oct 02, 2016 at 10:39:31AM +0300, Tomas Winkler wrote:
> > > > > > In tpm_del_char_device device_del is called prior to tpm2_shutdown
> > > > > > where it is still used.
> > > > > >
> > > > > > Fortunately, so far chip->dev was used only for printouts int
> > > > > > tpm2_shutdown flow, hence system didn't crash. But with the
> > > > > > introduction of runtime power management it will result in
> > > > > > shutting down the parent device while it still in use.
> > > > > >
> > > > > > Fixes: 20e0152393b41 ("tpm: fix crash in tpm_tis
> > > > > > deinitialization")
> > > > > > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> > > > >
> > > > > Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > > > > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > > >
> > > > Applied.
> > > 
> > > This patch is wrong, I though the comments were clear. All entry points to find
> > > the device must be deleted before we commit to shutting down the device.
> > > 
> > > You need to figure out some other way to solve your problem.
> > 
> > Please  be more specific regarding flows you think will be wrong  with
> > this patch, you must agree that the current code is broken even w/o
> > runtime pm.
> 
> Make the driver uncallable first. The worst race that can happen is that
> open("/dev/tpm0", ...) returns -EPIPE. I do not consider this fatal at
> all.

No responses for this reasonable proposal so I'll show what I mean:

/* Make the driver uncallable. */
down_write(&chip->ops_sem);
if (chip->flags & TPM_CHIP_FLAG_TPM2)
	tpm2_shutdown(chip, TPM2_SU_CLEAR);
chip->ops = NULL;
up_write(&chip->ops_sem);

cdev_del(&chip->cdev);
device_del(&chip->dev);

/* Make the chip unavailable. */
mutex_lock(&idr_lock);
idr_replace(&dev_nums_idr, NULL, chip->dev_num);
mutex_unlock(&idr_lock);

The worst thing that can happen is -EPIPE.

/Jarkko

  reply	other threads:[~2016-10-04  5:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-02  7:39 [PATCH] tpm: don't destroy chip device prematurely Tomas Winkler
2016-10-02 10:17 ` Jarkko Sakkinen
2016-10-02 10:24   ` Jarkko Sakkinen
2016-10-02 21:21     ` Jason Gunthorpe
2016-10-03  7:05       ` Winkler, Tomas
2016-10-03  7:38         ` Winkler, Tomas
2016-10-03 12:42           ` Jarkko Sakkinen
2016-10-03 16:03             ` Jason Gunthorpe
2016-10-03 17:30               ` Winkler, Tomas
2016-10-03 12:48         ` Jarkko Sakkinen
2016-10-04  5:19           ` Jarkko Sakkinen [this message]
2016-10-04 16:47             ` Jason Gunthorpe
2016-10-04 21:55               ` Winkler, Tomas
2016-10-04 23:10                 ` Jason Gunthorpe
2016-10-05  7:48                   ` Winkler, Tomas
2016-10-05 15:15                     ` Jarkko Sakkinen
2016-10-05 16:37                       ` Jason Gunthorpe
2016-10-05 17:11                     ` Jason Gunthorpe
2016-10-05 20:09                       ` Winkler, Tomas
2016-10-05 21:16                         ` Jason Gunthorpe
2016-10-06  0:43                           ` Winkler, Tomas
2016-10-06  2:07                             ` Jason Gunthorpe
2016-10-07 14:24                               ` Winkler, Tomas
2016-10-07 19:17                                 ` Jason Gunthorpe
2016-10-07 20:10                                   ` Winkler, Tomas
2016-10-08 10:47                                 ` Jarkko Sakkinen
2016-10-05 10:02               ` Jarkko Sakkinen
2016-10-05 16:27                 ` Jason Gunthorpe
2016-10-06 11:23                   ` Jarkko Sakkinen
2016-10-06 16:22                     ` Jason Gunthorpe
2016-10-06 16:46                       ` Jarkko Sakkinen
2016-10-05 10:09               ` Jarkko Sakkinen
2016-10-03 16:00         ` Jason Gunthorpe
2016-10-03 17:16           ` Winkler, Tomas
2016-10-03 17:30             ` Jason Gunthorpe

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=20161004051946.GA10572@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas.winkler@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).