From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S942936AbdAJTfd (ORCPT ); Tue, 10 Jan 2017 14:35:33 -0500 Received: from [195.159.176.226] ([195.159.176.226]:33194 "EHLO blaine.gmane.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S942776AbdAJTfb (ORCPT ); Tue, 10 Jan 2017 14:35:31 -0500 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: Ken Goldman Subject: Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager Date: Tue, 10 Jan 2017 14:29:08 -0500 Message-ID: References: <201701041612.v04GCfPK031525@wind.enjellic.com> <20170109231635.6wh25qoy7svcnys6@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 In-Reply-To: <20170109231635.6wh25qoy7svcnys6@intel.com> Cc: linux-security-module@vger.kernel.org, tpmdd-devel@lists.sourceforge.net Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/9/2017 6:16 PM, Jarkko Sakkinen wrote: > > Here's my cuts for the kernel: > > - Kernel virtualizes handle areas. It's mechanical. > - Kernel does not virtualize bodies. It's not mechanical. > - At least the first version of the RM will not do other than session > isolation for sessions. Is it correct that "bodies" are the parameter area of the commands and responses? if so, eventually something should virtualize getcapability. It may be safer in user space, but it can mask RM issues.