Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751651AbcJCHiy convert rfc822-to-8bit (ORCPT ); Mon, 3 Oct 2016 03:38:54 -0400 Received: from mga07.intel.com ([134.134.136.100]:30692 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750949AbcJCHit (ORCPT ); Mon, 3 Oct 2016 03:38:49 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,288,1473145200"; d="scan'208";a="15569988" From: "Winkler, Tomas" To: "Winkler, Tomas" , Jason Gunthorpe , Jarkko Sakkinen CC: "tpmdd-devel@lists.sourceforge.net" , "linux-kernel@vger.kernel.org" Subject: RE: [PATCH] tpm: don't destroy chip device prematurely Thread-Topic: [PATCH] tpm: don't destroy chip device prematurely Thread-Index: AQHSHJY7jYiWgZcWb0y7/x76d69Sl6CUwviAgAC3bgCAANJWAIAAChaQ Date: Mon, 3 Oct 2016 07:38:44 +0000 Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B542F46C1@hasmsx108.ger.corp.intel.com> References: <1475393971-12715-1-git-send-email-tomas.winkler@intel.com> <20161002101755.GA25844@intel.com> <20161002102455.GA27464@intel.com> <20161002212126.GA25872@obsidianresearch.com> <5B8DA87D05A7694D9FA63FD143655C1B542F466B@hasmsx108.ger.corp.intel.com> In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B542F466B@hasmsx108.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjg2MGQwYzQtY2RjYi00NjQwLTkwMDgtYmE5MTQ4NDc0MDg1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6ImVDaEFcL3NEVWFyQXZvT2xjdGtuXC9TSHhpUU44WEdvaHlnUTc0ejhuT1hKMD0ifQ== x-originating-ip: [10.184.70.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1941 Lines: 44 > > > 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 > > > > > > > > Tested-by: Jarkko Sakkinen > > > > Reviewed-by: Jarkko Sakkinen > > > > > > 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. I've looked to the registration code and it indeed has few more issues Maybe TPM_CHIP_FLAG_REGISTERED can be used for sealing the access to the device during deregistration, current usage is void. > Thanks > Tomas > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most engaging > tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > tpmdd-devel mailing list > tpmdd-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tpmdd-devel