From: Matt Fleming <matt@codeblueprint.co.uk>
To: Colin Ian King <colin.king@canonical.com>
Cc: "H . Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/efi: initialize status to ensure garbage is not returned on small size
Date: Mon, 1 Aug 2016 12:50:41 +0100 [thread overview]
Message-ID: <20160801115041.GD3636@codeblueprint.co.uk> (raw)
In-Reply-To: <ada10a97-f3d3-91af-51b8-6d2f973c95a1@canonical.com>
On Wed, 27 Jul, at 03:50:16PM, Colin Ian King wrote:
>
> I'd rather put extra guarding in rather than getting some potential
> garbage return from the stack, but I am playing it rather conservatively
> here.
I think that's sensible, I just wanted to confirm your rationale.
Thanks, applied.
prev parent reply other threads:[~2016-08-01 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 10:11 [PATCH] x86/efi: initialize status to ensure garbage is not returned on small size Colin King
2016-07-27 14:38 ` Matt Fleming
2016-07-27 14:50 ` Colin Ian King
2016-08-01 11:50 ` Matt Fleming [this message]
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=20160801115041.GD3636@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=colin.king@canonical.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox