From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Re: [PATCH] stackprot: Make our test a bit more complex
Date: Mon, 24 May 2021 20:58:04 -0400 [thread overview]
Message-ID: <20210525005804.GS17669@bill-the-cat> (raw)
In-Reply-To: <20210524185913.10422-1-trini@konsulko.com>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Mon, May 24, 2021 at 02:59:13PM -0400, Tom Rini wrote:
> With better compiler optimizations available, a compiler may see we do
> nothing with our buffer after calling memset and omit the call, thus
> causing us to not smash the stack. Add a comment to explain why we now
> also have a printf call, so that the test will pass as the memset will
> not be omitted.
>
> Reported-by: Marek Behún <marek.behun@nic.cz>
> Signed-off-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2021-05-25 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 18:59 [PATCH] stackprot: Make our test a bit more complex Tom Rini
2021-05-25 0:58 ` Tom Rini [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=20210525005804.GS17669@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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