linux-kernel - Re: [PATCH] x86/boot: Remove unused function __fortify

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240610162923.GGZmcp4zRfJcTghSeg@fat_crate.local>
Date: Mon, 10 Jun 2024 18:29:23 +0200
From: Borislav Petkov <bp@...en8.de>
To: Nikolay Borisov <nik.borisov@...e.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, kees@...nel.org
Subject: Re: [PATCH] x86/boot: Remove unused function __fortify_panic()

On Mon, Jun 10, 2024 at 02:57:22PM +0300, Nikolay Borisov wrote:
> That functino is only used when the kernel is compiled with
       ^^^^^^^^^

Please introduce a spellchecker into your patch creation workflow.

Like, run the thing through the spellchecker on the system or you can
even use my python script which checks patches and can do that for you:

https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=vp

> FORTIFY_SOURCE and when the kernel proper string.h header is used. The
> decompressor code doesn't use the kernel proper header but has local
> copy which doesn't contain any fortified implementations of the various
> string functions. As such __fortify_panic can never be called from the
> decompressor so let's remove it.

Yap, might as well whack it.

We can always resurrect it if it is really needed as it is trivial.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette