linux-kernel - Re: [PATCH v6 0/9] tpm: cleanup/fixes in existing event log support

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:   Sun, 20 Nov 2016 09:58:48 +0000
From:   Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To:     Jason Gunthorpe <jgunthorpe@...idianresearch.com>
Cc:     Nayna <nayna@...ux.vnet.ibm.com>,
        tpmdd-devel@...ts.sourceforge.net, peterhuewe@....de,
        tpmdd@...horst.net, linux-kernel@...r.kernel.org,
        linux-security-module@...r.kernel.org
Subject: Re: [PATCH v6 0/9] tpm: cleanup/fixes in existing event log support

On Sat, Nov 19, 2016 at 11:36:27AM -0700, Jason Gunthorpe wrote:
> On Tue, Nov 15, 2016 at 10:54:53AM -0800, Jarkko Sakkinen wrote:
> > On Tue, Nov 15, 2016 at 11:06:10AM -0700, Jason Gunthorpe wrote:
> > > On Tue, Nov 15, 2016 at 09:40:12AM -0800, Jarkko Sakkinen wrote:
> > > 
> > > > I applied fix from Colin. I for OF specific patches in this patch set
> > > > I do not have means to test the code paths that exercise OF specific
> > > > functionality. This is what worries me a bit. If I had tested-by from
> > > > someone running a system that can exercise those code paths, I would
> > > > be less worried.
> > > 
> > > I can probably check it next week on my OF systems that do not use event log
> > 
> > Thanks Jason. I'll apppend your Tested-by's to the commits when you're
> > done. Probably doing pull request in the latter part of next week.
> 
> What are we testing? Your master now? It will need the patch I just
> sent or it will fail for me.

$ git am -3 ~/Desktop/foo.txt 
Patch is empty. Was it split wrong?
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

I'm at the Heathrow airport boarding. Look it more properly later on

/Jarkko