public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-security-module@vger.kernel.org,
	tpmdd-devel@lists.sourceforge.net
Subject: Re: [tpmdd-devel] [PATCH 6/6] tpm2: add session handle context saving and restoring to the space code
Date: Fri, 10 Feb 2017 11:12:15 -0800	[thread overview]
Message-ID: <1486753935.2502.35.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170210191004.yv5hgnd3h5scj5zt@intel.com>

On Fri, 2017-02-10 at 21:10 +0200, Jarkko Sakkinen wrote:
> On Fri, Feb 10, 2017 at 08:17:11AM -0800, James Bottomley wrote:
> > On Fri, 2017-02-10 at 14:32 +0200, Jarkko Sakkinen wrote:
> > > On Wed, Feb 08, 2017 at 01:07:08PM +0200, Jarkko Sakkinen wrote:
> > > > From: James Bottomley <James.Bottomley@HansenPartnership.com>
> > [...] 
> > > > +static int tpm2_session_add(struct tpm_chip *chip, u32 handle)
> > > > +{
> > > > +	struct tpm_space *space = &chip->work_space;
> > > > +	int i;
> > > > +
> > > > +	for (i = 0; i < ARRAY_SIZE(space->session_tbl); i++)
> > > > +		if (space->session_tbl[i] == 0)
> > > > +			break;
> > > > +	if (i == ARRAY_SIZE(space->session_tbl)) {
> > > > +		dev_err(&chip->dev, "out of session slots\n");
> > > 
> > > This really should be dev_dbg.
> > 
> > This was my reply to the comment the last time:
> > 
> >     I can do that, but I think this should be higher than debug. 
> >  If
> >     this trips, something an application was doing will fail with a
> > non
> >     TPM error and someone may wish to investigate why.  Having a
> > kernel
> >     message would help with that (but they won't see it if it's
> > debug).
> > 
> >     I'm also leaning towards the idea that we should actually have
> > one
> >     more _tbl slot than we know the TPM does, so that if someone
> > goes
> >     over it's the TPM that gives them a real TPM out of memory
> > error
> >     rather than the space code returning -ENOMEM.
> > 
> >     If you agree, I think it should be four for both sessions_tbl
> > and
> >     context_tbl.
> > 
> > So I really don't think it should be debug.  Could we compromise on
> > dev_info?
> > 
> > James
> 
> Oops, I'm sorry about that. I use the release chaos as an excuse :-)
> I would lower it to dev_warn().

That works.  Do you want me to resend the patch?

James

  reply	other threads:[~2017-02-10 19:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 11:07 [PATCH 0/6] in-kernel resource manager Jarkko Sakkinen
2017-02-08 11:07 ` [PATCH 1/6] tpm: validate TPM 2.0 commands Jarkko Sakkinen
2017-02-08 11:07 ` [PATCH 2/6] tpm: export tpm2_flush_context_cmd Jarkko Sakkinen
2017-02-08 17:58   ` Jason Gunthorpe
2017-02-10  7:42     ` Jarkko Sakkinen
2017-02-08 11:07 ` [PATCH 3/6] tpm: infrastructure for TPM spaces Jarkko Sakkinen
2017-02-08 11:07 ` [PATCH 4/6] tpm: split out tpm-dev.c into tpm-dev.c and tpm-common-dev.c Jarkko Sakkinen
2017-02-08 11:07 ` [PATCH 5/6] tpm: expose spaces via a device link /dev/tpms<n> Jarkko Sakkinen
2017-02-08 11:07 ` [PATCH 6/6] tpm2: add session handle context saving and restoring to the space code Jarkko Sakkinen
2017-02-10  8:52   ` Jarkko Sakkinen
2017-02-10 16:11     ` James Bottomley
2017-02-10 19:07       ` [PATCH 6/6] tpm2: add session handle context saving and restoring to the space code' Jarkko Sakkinen
2017-02-10 12:32   ` [PATCH 6/6] tpm2: add session handle context saving and restoring to the space code Jarkko Sakkinen
2017-02-10 16:17     ` James Bottomley
2017-02-10 19:10       ` Jarkko Sakkinen
2017-02-10 19:12         ` James Bottomley [this message]
2017-02-10 22:48           ` [tpmdd-devel] " Jarkko Sakkinen
2017-02-10  8:53 ` [PATCH 0/6] in-kernel resource manager Jarkko Sakkinen

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=1486753935.2502.35.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@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