lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <202209131033.EDED655DA4@keescook> Date: Tue, 13 Sep 2022 10:34:21 -0700 From: Kees Cook <keescook@...omium.org> To: Rich Felker <dalias@...c.org> Cc: Yoshinori Sato <ysato@...rs.sourceforge.jp>, linux-sh@...r.kernel.org, Geert Uytterhoeven <geert@...ux-m68k.org>, Paul Mundt <lethal@...ux-sh.org>, linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH] sh: machvec: Use char[] for section boundaries On Thu, Sep 08, 2022 at 06:15:39PM -0400, Rich Felker wrote: > On Wed, Sep 07, 2022 at 04:43:45PM -0700, Kees Cook wrote: > > As done for other sections, define the extern as a character array, > > which relaxes many of the compiler-time object size checks, which would > > otherwise assume it's a single long. Solves the following build error: > > > > arch/sh/kernel/machvec.c: error: array subscript 'struct sh_machine_vector[0]' is partly outside array bounds of 'long int[1]' [-Werror=array-bounds]: => 105:33 > > LGMT. This is the approach I recommend for this general type of > mechanism. So, > > Acked-by: Rich Felker <dalias@...c.org> > > Since I haven't been on top of collating patches for upstreaming, I'd > be happy if anyone else wants to take this in their tree before I get > back to it. Great; thanks! I'll take it via my tree. :) -Kees -- Kees Cook
Powered by blists - more mailing lists