Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3057972imm; Mon, 10 Sep 2018 10:19:08 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbNWWNh6Ere/otRJsjIRCSfBixNYxMjaAx4F6g5RQ2nt5LV9sqUN22edroDYRP/9xUaxW2Z X-Received: by 2002:a63:3642:: with SMTP id d63-v6mr23526149pga.231.1536599948280; Mon, 10 Sep 2018 10:19:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536599948; cv=none; d=google.com; s=arc-20160816; b=NAv7wvNdyY8fFjCV95OLU+baoEsAFY3kgmqw7lQfsrsi7PPoj1kPZfhcMIoaUjPahL JnEW5sxMeOMGtKn6eTMtQXl02gBbKdwN0vo5JzjaXETnS6hgp+OpZ2xYpqFCTEOmxgmR E5efJY6M9kvuUsm98I5qEPiEf1A2YZnsGVKHZyPLcAXLpw9f43+X7tSmPa2UXlPsfZW2 3B8ds2jz9F70YLMDL0XZz9Lcunf1RG0+eEvPwW2L0p0n4eDe14xRroKdyXAluRzbtofo 683ApSW0VGgoCFG/D+GzoDZRWxPkzYkAEBDqnavWPG/6vX8js0VVCtoQAO+MpoW32nOg srNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:message-id:date:cc:to:from:subject; bh=Ou/+FKEPo4rmnEfrUwLXWcfokkVgczsliXJFBkHyppI=; b=MuTM6BqHwZoQNE293hQlV70b5xqOg5iaQZMLAp2T34gl00LIzDXaDvo/ntGVgDhq/M 9PWqXaSf06s07qW0881FTuZ9A9ZvFWnNutdyW+bx1yKxpbJkowWFwg+Jys5wa02nlTOt uSBsgCE7j7xEaFjEaym0eWQKIICa5AszuIWeNHWADzRmTC9YAtPlroGpQnKNkBYogkQD ZFXyVPIFhkDQLT5g0pviFN4+vWzguCNCrIsdLP856iuleBL4p1WgNEzhJVDntg6kf8ch HhsOW6ss/9dhlNC+qoARIQ4JLyRqc5dgXmSwIvHFgqjJDDbEye00tKKoc/gUl+bZODkj 8M+g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b4-v6si18080105pgg.537.2018.09.10.10.18.52; Mon, 10 Sep 2018 10:19:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728177AbeIJWN2 (ORCPT + 99 others); Mon, 10 Sep 2018 18:13:28 -0400 Received: from mga04.intel.com ([192.55.52.120]:49560 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727705AbeIJWN2 (ORCPT ); Mon, 10 Sep 2018 18:13:28 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Sep 2018 10:18:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.53,356,1531810800"; d="scan'208";a="262274801" Received: from tstruk-mobl1.jf.intel.com ([10.24.8.238]) by fmsmga006.fm.intel.com with ESMTP; 10 Sep 2018 10:18:22 -0700 Subject: [PATCH v6 0/2] tpm: add support for nonblocking operation From: Tadeusz Struk To: jarkko.sakkinen@linux.intel.com Cc: flihp@twobit.us, jgg@ziepe.ca, linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, tadeusz.struk@intel.com Date: Mon, 10 Sep 2018 10:18:22 -0700 Message-ID: <153659990230.2284.5511495299744743989.stgit@tstruk-mobl1.jf.intel.com> User-Agent: StGit/unknown-version MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The TCG SAPI specification [1] defines a set of functions, which allow applications to use the TPM device in either blocking or non-blocking fashion. Each command defined by the specification has a corresponding Tss2_Sys__Prepare() and Tss2_Sys__Complete() call, which together with Tss2_Sys_ExecuteAsync() is designed to allow asynchronous mode of operation. Currently the TPM driver supports only blocking calls, which doesn't allow asynchronous IO operations. This patch changes it and adds support for nonblocking write and a new poll function to enable applications, which want to take advantage of this feature. The new functionality can be tested using standard TPM tools implemented in [2], together with modified TCTI from [3], and an example application by Philip Tricca [4]. Here is a short description from Philip: "The example application `glib-tss2-event` uses a glib main event loop to create an RSA 2048 primary key in the TPM2 NULL hierarchy while using a glib timer event to time the operation. A GSource object is used to generate an event when the FD underlying the tss2 function call has data ready. While the application waits for an event indicating that the CreatePrimary operation is complete, it counts timer events that occur every 100ms. Once the CreatePrimary operation completes the number of timer events that occurred is used to make a rough calculation of the elapsed time. This value is then printed to the console. This takes ~300 lines of C code and requires no management or synchronization of threads. The glib GMainContext is "just a poll() loop" according to the glib documentation here: https://developer.gnome.org/programming-guidelines/stable/main-contexts.html.en and so supporting 'poll' is the easiest way to integrate with glib / gtk+. This is true of any other event system that relies on 'poll' instead of worker threads." [1] https://trustedcomputinggroup.org/wp-content/uploads/TSS_SAPI_Version-1.1_Revision-22_review_030918.pdf [2] https://github.com/tpm2-software/tpm2-tools [3] https://github.com/tstruk/tpm2-tss/tree/async [4] https://github.com/flihp/glib-tss2-async-example --- Changes in v6: - Changed commit message in the first patch to more specific. - Chenged labels names in tpm-interface.c Changes in v5: - Changed the workqueue allocation time back from the first user interface open to module init. Changes in v4: - Changed the way buffer_mutex is handled in nonblocking mode so that it is not held when write() returns to user space. Changes in v3: - Fixed problem reported by 0-dey kbuild test robot around __exitcall. It complained because there is a module_exit() in another file already. - Added info on example application from Philip Changes in v2: - Split the change into two separate patches. First patch adds a pointer to the space to the struct file_priv to have access to it from the async job. This is to avoid memory allocations on every write call. Now everything what's needed is in the file_priv struct. - Renamed the 'work' member of the timer to avoid confusion. Now there are 'timeout_work' and 'async_work'. - Removed the global wait queue and moved it to file_priv. - Only creating the work queue when the first file is opened. Tadeusz Struk (2): tpm: add ptr to the tpm_space struct to file_priv tpm: add support for nonblocking operation drivers/char/tpm/tpm-dev-common.c | 150 +++++++++++++++++++++++++++---------- drivers/char/tpm/tpm-dev.c | 22 +++-- drivers/char/tpm/tpm-dev.h | 19 +++-- drivers/char/tpm/tpm-interface.c | 1 drivers/char/tpm/tpm.h | 1 drivers/char/tpm/tpmrm-dev.c | 31 ++++---- 6 files changed, 152 insertions(+), 72 deletions(-) -- TS