Received: by 10.223.164.202 with SMTP id h10csp1969338wrb; Sat, 11 Nov 2017 21:28:24 -0800 (PST) X-Google-Smtp-Source: AGs4zMZjRHo/FvAdDE0stQOPBOgvQlitQxvSbLi7RrPdqifEljpnvncYpNVWxB+IfZfrM0wQvVXI X-Received: by 10.101.81.139 with SMTP id h11mr5016231pgq.233.1510464504756; Sat, 11 Nov 2017 21:28:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510464504; cv=none; d=google.com; s=arc-20160816; b=Gw+OvnVfSjOVq5e/KQf4qqr0w8rtnFU7F3m/byj/ILED3LgwswbGLc9AgGsWjNK4kt GTMqnW84qUSpZGYKxfEith1Rgtmpi75izPsO4LEIBvZhNzb3F9zQH/IAwmb9CtgvXswS Xkui6lbzEhi2gVu9H/G7NwlNvl+XM1+g6Ky/xHI50nHwXWkLZPzZksmkWRj0DYpI9bw+ cHrKJHW4JT5sFUX7p2sML1uMhXXKthgdBsUIIEScYyDdmhK7KU9FAV+vwG9knTVdh3NT mQOHVAh/XaTd2N8QObFlgbAmAGKWCvwKnoivczthTyw4vC821GZaZOyOXgky3Et7dEg6 EHhA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=O/dfpxQDI8450qS6r+i9ZlPzBe2jhnVt2A8yEUdk6Ik=; b=esa4n643Sswn8+JHtK8Pu/wlI8ZAIss2vpJxUury4NgIDOnMcwM5xctCIqax0oBnBK C1PtW2M3GoN7YrIAu8h50SApu3+mwmJsxUuQ5Jj9GAbsAkW+zf/IENZ+HbxIZjOIMMxN nTxb3ur0nmQmhNNA00zexrYwAhUftRxFMhoelma/kuToq0lBK/AFESUVYtiS+TFxpazR hRLu08CczEJmaDuCYYTr1g5UHWgUX21VDLQbrcNUxVeCzQ1NHFGzWCMKG0t2iRnuKgRS 8CMw5X2h6zVSxcfePrm4WKnFTpUTI55loFh9O6pEfPHZgQqeVPfIl3za27N1gQN15Nv9 JfUw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=LAkLDQ4G; 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=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l24si1573238pgo.729.2017.11.11.21.28.12; Sat, 11 Nov 2017 21:28:24 -0800 (PST) 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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=LAkLDQ4G; 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=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751522AbdKLF1g (ORCPT + 87 others); Sun, 12 Nov 2017 00:27:36 -0500 Received: from mail-it0-f66.google.com ([209.85.214.66]:33011 "EHLO mail-it0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750798AbdKLF1c (ORCPT ); Sun, 12 Nov 2017 00:27:32 -0500 Received: by mail-it0-f66.google.com with SMTP id n134so6975577itg.0; Sat, 11 Nov 2017 21:27:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=O/dfpxQDI8450qS6r+i9ZlPzBe2jhnVt2A8yEUdk6Ik=; b=LAkLDQ4GAQQsS8WF2wCSjfndeUuT/RhqlLxb6UYt/e0fBKapCRlgvgKXLgeOyjt7ND 0lva70uUuilIe9cQmEaPwF/6g4P7X5Y9ayqIHEAe/KOjlZ0rumpHXCH1cDwKj8aKw0mN 4JW+URJoZ14XJxKOmej3DRqPNhxZ7twqJdTMnb4DcCfZHJ4xUqEFSV0dtaNW3CJCmHKA TALQ3CMlHFH5Up7MHy51q9QPEstoNFjjxiqtrtgjKcoaSTrrM5pOvMUcGAexelxd2rOJ bJMUtrR1WUltTPqPRDTyQYlNjZxjB1v92MX+3V/FJlF7BS6SENOWmfk4L7dj5qs/Q7v9 DvlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=O/dfpxQDI8450qS6r+i9ZlPzBe2jhnVt2A8yEUdk6Ik=; b=BVq5r1/F5HYRfy4s54uXFvakzsSVFkxiPh7iD91Hu12SJ283MMZ6xRSV9xyNEGgtrs WAZFv27NwiaU6RF+fcqjwcwUOF8RJQ/PrAyNz68kyZgNn6xoXIB4QhN5oyDxZrBw6Aj1 voIUSpHlLylCatC7qtGFJKjNJr+0OX3zyRlP8R+FCqH3a3zq1NSC5a6bAknR40+uxp8w UJVeBj5axQ5czE1rWZJhPn3ILrsxa6E82uKPQfyVoJoi6yOiZhYXODtnR8P8wAKcGhu7 MbBaIEF6IhsFskj2YL73Pgzdx/MATXww0H1Ad7WNU62aQZu23u+eLdht/3SQlQSdEr7c yFUQ== X-Gm-Message-State: AJaThX6v8bNWeVRRO98SPldLELbUT+T7ZtB1UwL6AuDhZSlChgm0/SLf uq0h2t/vstQMr+T1a38LFp5XDdb+62X5Vj57nkBcQkW3LLo= X-Received: by 10.36.173.72 with SMTP id a8mr5733530itj.89.1510464451090; Sat, 11 Nov 2017 21:27:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.182.140 with HTTP; Sat, 11 Nov 2017 21:27:30 -0800 (PST) In-Reply-To: <20171109162947.GJ7063@ziepe.ca> References: <20171031200503.GC18578@ziepe.ca> <20171105110506.usxmuzrvcjvxahr6@linux.intel.com> <20171106022704.GD26011@ziepe.ca> <20171107160404.GG21466@ziepe.ca> <20171109162947.GJ7063@ziepe.ca> From: PrasannaKumar Muralidharan Date: Sun, 12 Nov 2017 10:57:30 +0530 Message-ID: Subject: Re: [PATCH v2] tpm: Move Linux RNG connection to hwrng To: Jason Gunthorpe Cc: Jarkko Sakkinen , Stefan Berger , linux-integrity@vger.kernel.org, David Howells , Herbert Xu , Dmitry Kasatkin , open list , "open list:INTEGRITY MEASUREMENT ARCHITECTURE (IMA)" , "open list:KEYS-TRUSTED" , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , James Morris , Matt Mackall , David Safford , Mimi Zohar , "Serge E. Hallyn" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jason, On 9 November 2017 at 21:59, Jason Gunthorpe wrote: > On Thu, Nov 09, 2017 at 09:49:33PM +0530, PrasannaKumar Muralidharan wrote: >> Hi Jason, >> >> On 7 November 2017 at 21:34, Jason Gunthorpe wrote: >> > On Tue, Nov 07, 2017 at 08:50:44AM +0530, PrasannaKumar Muralidharan wrote: >> > >> >> I am assuming you are talking about the following patches - using >> >> struct tpm_chip instead of chip number and this patch. >> > >> > yes >> > >> >> I won't be able to test if struct tpm_chip usage as I don't have >> >> multiple tpm hw in one machine. In case of tpm rng changes I can test >> >> only the lifecycle of tpm rng device. Is that enough? I feel my test >> >> will be limited. Please provide your thoughts on this. >> > >> > That is certainly better than no testing. >> >> The struct tpm_chip patch partially applied on linux next. I had to >> manually change the code. In qemu tpm rng device did not show up on >> loading tpm module. My laptop has tpm hw but Linux next did not work >> properly in that. All my console were getting spammed with some USB >> log message and I could not do anything. X did not start either. I >> could not debug the issue as the logs were printing infinitely. Will >> get little more time this weekend. Will do a proper test and provide >> you the result. > > Test against 4.15-rc, here are the two patches > > https://github.com/jgunthorpe/linux/tree/tpm > > Pull from here and merge the latest rc and you will probably have a > bootable system. > > Jason Applied this patch on v4.14-rc4. Able to get data from tpm rng (/dev/hwrng with tpm as the chosen rng). This patch works fine. Its just a basic test though. Tested-by: PrasannaKumar Muralidharan Regards, PrasannaKumar From 1583606778937322564@xxx Thu Nov 09 16:31:52 +0000 2017 X-GM-THRID: 1582805030856907824 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread