On Tue, Jun 6, 2017 at 2:49 AM, Will Deacon <will.dea...@arm.com> wrote:
> On Tue, Jun 06, 2017 at 10:43:52AM +0100, Catalin Marinas wrote:
>> On Mon, Jun 05, 2017 at 09:52:30PM -0700, Kees Cook wrote:
>> > Adjust vdso_{start|end} to be char arrays to avoid compile-time analysis
>> > that flags "too large" memcmp() calls with CONFIG_FORTIFY_SOURCE.
>> >
>> > Suggested-by: Mark Rutland <mark.rutl...@arm.com>
>> > Signed-off-by: Kees Cook <keesc...@chromium.org>
>> > Cc: Catalin Marinas <catalin.mari...@arm.com>
>> > Cc: Will Deacon <will.dea...@arm.com>
>> > Cc: Jisheng Zhang <jszh...@marvell.com>
>>
>> Acked-by: Catalin Marinas <catalin.mari...@arm.com>
>
> Kees -- I'm assuming this series is going via some other tree, but let me
> know if you want this patch to go via arm64.Greg has picked up the staging fix, so it's fine if it goes via other trees. I think akpm will pick up anything that is left over. So, yeah, please take it via arm64. (And I need to fix git send-email to actually Cc people on "Suggested-by", etc... hmm) -Kees -- Kees Cook Pixel Security
