From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] tpm: vtpm_proxy: Do not run tpm2_shutdown
Date: Thu, 25 May 2017 14:44:14 -0600 [thread overview]
Message-ID: <20170525204414.GA13742@obsidianresearch.com> (raw)
In-Reply-To: <9ff88c24-ca7a-1867-7284-17689fdac655@linux.vnet.ibm.com>
On Thu, May 25, 2017 at 04:32:50PM -0400, Stefan Berger wrote:
> It doesn't hang. Everything is torn down immediately. What is primarily
> annoying are these two log messages:
> tpm tpm0: tpm_transmit: tpm_send: error -32
> tpm tpm0: transmit returned -32 while stopping the TPM
I think it would be better to change the core to suppress that logging
if the FD is closed.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Stefan Berger
<stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] tpm: vtpm_proxy: Do not run tpm2_shutdown
Date: Thu, 25 May 2017 14:44:14 -0600 [thread overview]
Message-ID: <20170525204414.GA13742@obsidianresearch.com> (raw)
In-Reply-To: <9ff88c24-ca7a-1867-7284-17689fdac655-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
On Thu, May 25, 2017 at 04:32:50PM -0400, Stefan Berger wrote:
> It doesn't hang. Everything is torn down immediately. What is primarily
> annoying are these two log messages:
> tpm tpm0: tpm_transmit: tpm_send: error -32
> tpm tpm0: transmit returned -32 while stopping the TPM
I think it would be better to change the core to suppress that logging
if the FD is closed.
Jason
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: jarkko.sakkinen@linux.intel.com,
tpmdd-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tpm: vtpm_proxy: Do not run tpm2_shutdown
Date: Thu, 25 May 2017 14:44:14 -0600 [thread overview]
Message-ID: <20170525204414.GA13742@obsidianresearch.com> (raw)
In-Reply-To: <9ff88c24-ca7a-1867-7284-17689fdac655@linux.vnet.ibm.com>
On Thu, May 25, 2017 at 04:32:50PM -0400, Stefan Berger wrote:
> It doesn't hang. Everything is torn down immediately. What is primarily
> annoying are these two log messages:
> tpm tpm0: tpm_transmit: tpm_send: error -32
> tpm tpm0: transmit returned -32 while stopping the TPM
I think it would be better to change the core to suppress that logging
if the FD is closed.
Jason
next prev parent reply other threads:[~2017-05-25 20:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 13:12 [PATCH] tpm: vtpm_proxy: Do not run tpm2_shutdown Stefan Berger
2017-05-25 13:12 ` Stefan Berger
2017-05-25 13:12 ` Stefan Berger
2017-05-25 15:50 ` Jason Gunthorpe
2017-05-25 15:50 ` Jason Gunthorpe
2017-05-25 15:50 ` Jason Gunthorpe
2017-05-25 20:04 ` Stefan Berger
2017-05-25 20:04 ` Stefan Berger
2017-05-25 20:09 ` Jason Gunthorpe
2017-05-25 20:09 ` Jason Gunthorpe
2017-05-25 20:32 ` Stefan Berger
2017-05-25 20:32 ` Stefan Berger
2017-05-25 20:44 ` Jason Gunthorpe [this message]
2017-05-25 20:44 ` Jason Gunthorpe
2017-05-25 20:44 ` Jason Gunthorpe
2017-05-25 20:54 ` Stefan Berger
2017-05-25 20:54 ` Stefan Berger
2017-05-25 20:54 ` Stefan Berger
2017-05-25 21:00 ` Jason Gunthorpe
2017-05-25 21:00 ` Jason Gunthorpe
2017-05-25 22:33 ` Jarkko Sakkinen
2017-05-25 22:33 ` Jarkko Sakkinen
2017-05-25 22:33 ` Jarkko Sakkinen
2017-05-25 23:34 ` Stefan Berger
2017-05-25 23:34 ` Stefan Berger
2017-05-25 23:34 ` 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=20170525204414.GA13742@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=linux-security-module@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 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.