linux-kernel - Re: [PATCH v3] Add "shutdown" to "struct class".

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 18 May 2017 08:20:53 -0700
From:   Josh Zimmerman <joshz@...gle.com>
To:     "Winkler, Tomas" <tomas.winkler@...el.com>
Cc:     Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        "tpmdd-devel@...ts.sourceforge.net" 
        <tpmdd-devel@...ts.sourceforge.net>
Subject: Re: [PATCH v3] Add "shutdown" to "struct class".

Are there any more changes any of you would like to see in this patch?

Thanks!
Josh


On Mon, May 15, 2017 at 1:49 PM, Winkler, Tomas <tomas.winkler@...el.com> wrote:
>
>
>> -----Original Message-----
>> From: Jason Gunthorpe [mailto:jgunthorpe@...idianresearch.com]
>> Sent: Monday, May 15, 2017 20:46
>> To: Josh Zimmerman <joshz@...gle.com>
>> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>; linux-
>> kernel@...r.kernel.org; Winkler, Tomas <tomas.winkler@...el.com>; Jarkko
>> Sakkinen <jarkko.sakkinen@...ux.intel.com>; tpmdd-
>> devel@...ts.sourceforge.net
>> Subject: Re: [PATCH v3] Add "shutdown" to "struct class".
>>
>> On Mon, May 15, 2017 at 10:39:08AM -0700, Josh Zimmerman wrote:
>> > (Continuing thread from patch v1)
>> > > > On Sat, May 13, 2017 at 12:43:11PM +0000, Winkler, Tomas wrote:
>> > > > > > The TPM class has some common shutdown code that must be
>> > > > > > executed for all drivers. This adds some needed functionality
>> > > > > > for that
>> > > > >
>> > > > > The issue with this is, that on some platforms the only storage
>> > > > > can be eMMC and TPM is using it,. It has to be ensured that the
>> > > > > storage device won't go down before TPM2_shutdown is called.
>> > > > > And there is no direct device hierarchy to ensure an orderly
>> shutdown.
>> > > >
>> > > > Something will have to use the new device links stuff to define
>> > > > that dependency, but that seems unrelated to this patch?
>> > >
>> > >
>> > > Yep, it's not directly related to this specific patch, this is more relevant
>> particularly to TPM2_shutdown.
>> >
>> > Jason, do you want me to do that in my patch on the tpmdd-devel list?
>> > If so, mind giving me a documentation pointer or two? I'm not familiar
>> > with this area.
>>
>> No.. Ordering power management events is something someone with
>> knowledge of the specific emmc platform is going to have to tackle..
>> It isn't really a core problem, platform specific code will have to setup the
>> needed device links to order power management properly..
>
> eMMC is just an example, that can be other storage device (ufs, nvme) and some type of abstraction of underlying storage
> dependency would be required. I just wanted to put it on the table, not sure it has to be solved in this round.
> Tomas
>
>
>
>
>>
>> Jason