From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Matthew Garrett <mjg59-JW9irJGTvgXQT0dZR+AlfA@public.gmane.org>
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] Fix unallocated memory access in TPM eventlog code
Date: Tue, 1 Mar 2016 17:03:02 -0700 [thread overview]
Message-ID: <20160302000302.GA447@obsidianresearch.com> (raw)
In-Reply-To: <1456873414-6127-1-git-send-email-mjg59-JW9irJGTvgXQT0dZR+AlfA@public.gmane.org>
On Tue, Mar 01, 2016 at 03:03:34PM -0800, Matthew Garrett wrote:
> COmmit 0cc698 added support for handling endian fixups in the event log code
> but broke the binary log file in the process. Keep the endian code, but read
> the event data from the actual event rather than from unallocated RAM.
This patch is doing the same thing?
https://git.kernel.org/cgit/linux/kernel/git/jmorris/linux-security.git/commit/drivers/char/tpm/tpm_eventlog.c?h=next&id=186d124f07da193a8f47e491af85cb695d415f2f
Already on it's way to mainline.
> - for (i = 0; i < sizeof(struct tcpa_event) + temp_event.event_size; i++)
> + for (i = 0; i < sizeof(struct tcpa_event); i++)
> + seq_putc(m, tempPtr[i]);
> +
> + tempPtr = (char *)&event->event_data;
> +
> + for (i = 0; i < temp_event.event_size; i++)
> seq_putc(m, tempPtr[i]);
Though this does look more elegant.
Jason
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
next prev parent reply other threads:[~2016-03-02 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 23:03 [PATCH] Fix unallocated memory access in TPM eventlog code Matthew Garrett
[not found] ` <1456873414-6127-1-git-send-email-mjg59-JW9irJGTvgXQT0dZR+AlfA@public.gmane.org>
2016-03-02 0:03 ` Jason Gunthorpe [this message]
[not found] ` <20160302000302.GA447-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-03-02 0:22 ` Matthew Garrett
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=20160302000302.GA447@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=mjg59-JW9irJGTvgXQT0dZR+AlfA@public.gmane.org \
--cc=stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.