[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 6 Jun 2017 09:11:13 -0700
From: Kees Cook <keescook@...omium.org>
To: Will Deacon <will.deacon@....com>
Cc: Catalin Marinas <catalin.marinas@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jisheng Zhang <jszhang@...vell.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/6] arm64, vdso: Define vdso_{start,end} as array
On Tue, Jun 6, 2017 at 2:49 AM, Will Deacon <will.deacon@....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.rutland@....com>
>> > Signed-off-by: Kees Cook <keescook@...omium.org>
>> > Cc: Catalin Marinas <catalin.marinas@....com>
>> > Cc: Will Deacon <will.deacon@....com>
>> > Cc: Jisheng Zhang <jszhang@...vell.com>
>>
>> Acked-by: Catalin Marinas <catalin.marinas@....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
Powered by blists - more mailing lists