[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e42c4984-d4a2-45b1-b93d-7471000766b7@quicinc.com>
Date: Thu, 30 May 2024 09:23:36 -0700
From: Jeff Johnson <quic_jjohnson@...cinc.com>
To: Nikolay Borisov <nik.borisov@...e.com>,
Thomas Gleixner
<tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov
<bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, <x86@...nel.org>,
Kees Cook <keescook@...omium.org>, "H. Peter Anvin" <hpa@...or.com>
CC: <linux-kernel@...r.kernel.org>, <linux-hardening@...r.kernel.org>,
<kernel-janitors@...r.kernel.org>
Subject: Re: [PATCH] x86/boot: add prototype for __fortify_panic()
On 5/30/2024 8:42 AM, Nikolay Borisov wrote:
>
>
> On 29.05.24 г. 21:09 ч., Jeff Johnson wrote:
>> As discussed in [1] add a prototype for __fortify_panic() to fix the
>> 'make W=1 C=1' warning:
>>
>> arch/x86/boot/compressed/misc.c:535:6: warning: symbol '__fortify_panic' was not declared. Should it be static?
>
> Actually doesn't it make sense to have this defined under ../string.h ?
> Actually given that we don't have any string fortification under the
> boot/ why have the fortify _* functions at all ?
I'll let Kees answer these questions since I just took guidance from him :)
/jeff
Powered by blists - more mailing lists