[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170209215441.GA3131@obsidianresearch.com>
Date: Thu, 9 Feb 2017 14:54:41 -0700
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Ken Goldman <kgoldman@...ibm.com>, greg@...ellic.com,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
tpmdd-devel@...ts.sourceforge.net
Subject: Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session
exhaustion
On Thu, Feb 09, 2017 at 11:29:51AM -0800, James Bottomley wrote:
> On Thu, 2017-02-09 at 12:04 -0700, Jason Gunthorpe wrote:
> > On Thu, Feb 09, 2017 at 05:19:22PM +0200, Jarkko Sakkinen wrote:
> > > The current patch set does not define policy. The simple policy
> > > addition that could be added soon is the limit of connections
> > > because it is easy to implement in non-intrusive way.
> >
> > It is also trivial for a userspace RM to limit the number of sessions
> > or connections or otherwise to manage this limitation. It is hard to
> > see why we'd need kernel support for this.
>
> Because the kernel is a primary TPM user.
When I said 'this' I meant a kernel policy to limit the number of
user connections.
Jason
Powered by blists - more mailing lists