[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACdnJuvkrMCbOwqkWUOZunXmu1AwfRpjNp3OAfqR2y0O+OK5Fw@mail.gmail.com>
Date: Wed, 25 Mar 2020 13:21:14 -0700
From: Matthew Garrett <mjg59@...gle.com>
To: Ross Philipson <ross.philipson@...cle.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
linux-doc@...r.kernel.org, dpsmith@...rtussolutions.com,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, trenchboot-devel@...glegroups.com
Subject: Re: [RFC PATCH 10/12] x86: Secure Launch adding event log securityfs
On Wed, Mar 25, 2020 at 12:43 PM Ross Philipson
<ross.philipson@...cle.com> wrote:
>
> From: "Daniel P. Smith" <dpsmith@...rtussolutions.com>
>
> The late init functionality registers securityfs nodes to allow fetching
> of and writing events to the late launch TPM log.
Is there a reason we would want this exposed separately from the
regular event log, rather than just appending it there?
> +static ssize_t sl_evtlog_write(struct file *file, const char __user *buf,
> + size_t datalen, loff_t *ppos)
> +{
What's expected to be writing to this?
Powered by blists - more mailing lists