From: Kees Cook <keescook@chromium.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH v4] ARM: decompressor: simplify libfdt builds
Date: Thu, 23 Apr 2020 10:52:04 -0700 [thread overview]
Message-ID: <202004231051.5DF870A@keescook> (raw)
In-Reply-To: <20200422075854.GK25745@shell.armlinux.org.uk>
On Wed, Apr 22, 2020 at 08:58:54AM +0100, Russell King - ARM Linux admin wrote:
> On Wed, Apr 22, 2020 at 09:44:38AM +0200, Geert Uytterhoeven wrote:
> > Is there a real reason this is only applied to a subset of the C object
> > files, and not to all of them? Or have we been lucky so far, by not
> > triggering the issue in decompressed.c, misc.c, and string.c (yet)?
>
> I don't remember the details. See commit 7f66cd3f5420, which came from
> Kees which introduced this.
Just to clarify: the original change was just removing it where it was
detected in the then-current build. I was going for the least invasive
change to the build system.
--
Kees Cook
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-23 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200419191958.208600-1-masahiroy@kernel.org>
2020-04-22 7:44 ` [PATCH v4] ARM: decompressor: simplify libfdt builds Geert Uytterhoeven
2020-04-22 7:58 ` Russell King - ARM Linux admin
2020-04-23 17:52 ` Kees Cook [this message]
2020-04-22 12:30 ` Masahiro Yamada
2020-04-22 12:38 ` Russell King - ARM Linux admin
2020-04-22 12:56 ` Geert Uytterhoeven
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=202004231051.5DF870A@keescook \
--to=keescook@chromium.org \
--cc=ard.biesheuvel@linaro.org \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=masahiroy@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;
as well as URLs for NNTP newsgroup(s).