From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sahil Rihan <srihan@fb.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
Alexei Starovoitov <ast@fb.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tpm: allow TCPA log area to be empty
Date: Tue, 27 Mar 2018 11:05:02 +0300 [thread overview]
Message-ID: <20180327080502.GA11855@linux.intel.com> (raw)
In-Reply-To: <49C2A39F-C9ED-4620-82C9-C0919DA3F2CD@fb.com>
On Tue, Mar 27, 2018 at 12:07:14AM +0000, Sahil Rihan wrote:
> > On 3/22/18, 7:20 AM, "Jarkko Sakkinen" <jarkko.sakkinen@linux.intel.com> wrote:
> >
> > On Tue, 2018-03-20 at 22:29 +0000, Sahil Rihan wrote:
> > > > On 3/19/18, 2:25 PM, "Jarkko Sakkinen" <jarkko.sakkinen@linux.intel.com>
> > > > wrote:
> > > >
> > > > Sahil, would you care to try if this fixes the issue that you are
> > > > having or not?
> > >
> > > Yes, we can test this out. Might take a day or two.
> >
> > Awesome, thank you. I'll add
> >
> > Reported-by: Sahil Rihan <srihan@fb.com>
> >
> > if that is OK for you?
>
> Jarkko,
>
> We applied your patch to a 4.11 kernel (unfortunately not the latest upstream) and were able to confirm that the char device is now being created correctly. The sysfs enabled node is also present.
>
> And yes, please add the "Reported-by" line.
>
> Thanks,
> Sahil
And also
Tested-by: Sahil Rihan <srihan@fb.com>
?
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] tpm: allow TCPA log area to be empty
Date: Tue, 27 Mar 2018 11:05:02 +0300 [thread overview]
Message-ID: <20180327080502.GA11855@linux.intel.com> (raw)
In-Reply-To: <49C2A39F-C9ED-4620-82C9-C0919DA3F2CD@fb.com>
On Tue, Mar 27, 2018 at 12:07:14AM +0000, Sahil Rihan wrote:
> > On 3/22/18, 7:20 AM, "Jarkko Sakkinen" <jarkko.sakkinen@linux.intel.com> wrote:
> >
> > On Tue, 2018-03-20 at 22:29 +0000, Sahil Rihan wrote:
> > > > On 3/19/18, 2:25 PM, "Jarkko Sakkinen" <jarkko.sakkinen@linux.intel.com>
> > > > wrote:
> > > >
> > > > Sahil, would you care to try if this fixes the issue that you are
> > > > having or not?
> > >
> > > Yes, we can test this out. Might take a day or two.
> >
> > Awesome, thank you. I'll add
> >
> > Reported-by: Sahil Rihan <srihan@fb.com>
> >
> > if that is OK for you?
>
> Jarkko,
>
> We applied your patch to a 4.11 kernel (unfortunately not the latest upstream) and were able to confirm that the char device is now being created correctly. The sysfs enabled node is also present.
>
> And yes, please add the "Reported-by" line.
>
> Thanks,
> Sahil
And also
Tested-by: Sahil Rihan <srihan@fb.com>
?
/Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-03-27 8:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 16:16 [PATCH] tpm: allow TCPA log area to be empty Jarkko Sakkinen
2018-03-10 16:16 ` Jarkko Sakkinen
2018-03-12 11:09 ` Jarkko Sakkinen
2018-03-12 11:09 ` Jarkko Sakkinen
2018-03-12 15:02 ` Jason Gunthorpe
2018-03-12 15:02 ` Jason Gunthorpe
2018-03-16 12:55 ` Jarkko Sakkinen
2018-03-16 12:55 ` Jarkko Sakkinen
2018-03-19 2:13 ` Jason Gunthorpe
2018-03-19 2:13 ` Jason Gunthorpe
2018-03-19 21:24 ` Jarkko Sakkinen
2018-03-19 21:24 ` Jarkko Sakkinen
2018-03-20 22:29 ` Sahil Rihan
2018-03-20 22:29 ` Sahil Rihan
2018-03-22 14:20 ` Jarkko Sakkinen
2018-03-22 14:20 ` Jarkko Sakkinen
2018-03-27 0:07 ` Sahil Rihan
2018-03-27 0:07 ` Sahil Rihan
2018-03-27 8:05 ` Jarkko Sakkinen [this message]
2018-03-27 8:05 ` Jarkko Sakkinen
2018-03-27 15:37 ` Sahil Rihan
2018-03-27 15:37 ` Sahil Rihan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180327080502.GA11855@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=ast@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=srihan@fb.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.