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 15:00:48 -0600 [thread overview]
Message-ID: <20170525210048.GA14592@obsidianresearch.com> (raw)
In-Reply-To: <cf746443-5ef5-211f-6b62-a5d4d66e27fd@linux.vnet.ibm.com>
On Thu, May 25, 2017 at 04:54:01PM -0400, Stefan Berger wrote:
> This particular command will never reach anyone listening on the proxy's
> file descriptor since the tear-down only begins when the front- and backend
> are closed.
> The logging happens somewhere else than where the error occurs. What is the
> best way to suppress the logging? Remove it entirely -- probably not.
> Return a special error code that doesn't get logged?
Error code would be my choice.
> that indicates this condition? It's not clear to me. Why not just
> prevent the command from being sent if it will never reach its
> intended destination
There are many cases where the vtpm shutdown can race with something
else, if the logging for this is bothersome it should be fixed
directly.
Adding strange special case flags is confusing as to the purpose - eg
your commit message didn't even say this is only about fixing some
noisy logging.
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
next prev parent reply other threads:[~2017-05-25 21:00 UTC|newest]
Thread overview: 10+ 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 15:50 ` Jason Gunthorpe
2017-05-25 20:04 ` Stefan Berger
2017-05-25 20:09 ` Jason Gunthorpe
2017-05-25 20:32 ` Stefan Berger
2017-05-25 20:44 ` Jason Gunthorpe
2017-05-25 20:54 ` Stefan Berger
2017-05-25 21:00 ` Jason Gunthorpe [this message]
2017-05-25 22:33 ` Jarkko Sakkinen
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=20170525210048.GA14592@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 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).