On 11/11/2018 12:35 PM, Greg KH wrote:
On Sun, Nov 11, 2018 at 11:53:20AM -0800, Dan Williams wrote:
On Sun, Nov 11, 2018 at 11:32 AM Greg KH wrote:
On Thu, Nov 08, 2018 at 10:06:50AM -0800, Alexander Duyck wrote:
Introduce four new variants of the async_schedule_ functions that allow
On Sun, Nov 11, 2018 at 12:35 PM Greg KH wrote:
>
> On Sun, Nov 11, 2018 at 11:53:20AM -0800, Dan Williams wrote:
> > On Sun, Nov 11, 2018 at 11:32 AM Greg KH wrote:
[..]
> This would be a great time for some other people to do that review :)
Message received, I'll block some time.
On 11/11/18 12:33 PM, Greg KH wrote:
When I see new major patches show up from an Intel developer without
_any_ other review from anyone else, directed at me, I get suspicious it
is happening again.
Hi Greg,
Please note that I reviewed this patch four days ago. See also
On Sun, Nov 11, 2018 at 11:53:20AM -0800, Dan Williams wrote:
> On Sun, Nov 11, 2018 at 11:32 AM Greg KH wrote:
> >
> > On Thu, Nov 08, 2018 at 10:06:50AM -0800, Alexander Duyck wrote:
> > > Introduce four new variants of the async_schedule_ functions that allow
> > > scheduling on a specific
On Sun, Nov 11, 2018 at 08:59:03PM +0100, Pavel Machek wrote:
> On Sun 2018-11-11 11:32:08, Greg KH wrote:
> > On Thu, Nov 08, 2018 at 10:06:50AM -0800, Alexander Duyck wrote:
> > > Introduce four new variants of the async_schedule_ functions that allow
> > > scheduling on a specific NUMA node.
>
> > Traditionally there is a single master key for the system, which would
> > be sealed to a set of boot time PCR values. After decrypting all of
> > the encrypted keys, the master key would be removed from the keyring
> > and a PCR extended. Extending a PCR would prevent the master key from
>
On Thu, Nov 08, 2018 at 10:06:50AM -0800, Alexander Duyck wrote:
> Introduce four new variants of the async_schedule_ functions that allow
> scheduling on a specific NUMA node.
>
> The first two functions are async_schedule_near and
> async_schedule_near_domain end up mapping to async_schedule
[ add keyrings and lkml ]
On Sun, Nov 11, 2018 at 9:28 AM Mimi Zohar wrote:
>
> On Fri, 2018-11-09 at 15:13 -0700, Dave Jiang wrote:
> > In order to make nvdimm more secure, encrypted keys will be used instead of
> > clear text keys. A master key will be created to seal encrypted nvdimm
> >
On Fri, 2018-11-09 at 15:13 -0700, Dave Jiang wrote:
> In order to make nvdimm more secure, encrypted keys will be used instead of
> clear text keys. A master key will be created to seal encrypted nvdimm
> keys. The master key can be a trusted key generated from TPM 2.0 or a less
> secure user
