linux-kernel - Fwd: Incorrect thinlto cache directory path in Makefile

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-next>] [day] [month] [year] [list]

Date: Sat, 11 May 2024 18:18:38 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Kernel Build System <linux-kbuild@...r.kernel.org>
Cc: Sami Tolvanen <samitolvanen@...gle.com>,
	Kees Cook <keescook@...omium.org>,
	Masahiro Yamada <masahiroy@...nel.org>,
	Xu Zhen <xuzhen@...tmail.com>
Subject: Fwd: Incorrect thinlto cache directory path in Makefile

Hi,

Xu Zhen <xuzhen@...tmail.com> reported on Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=218825) thinlto build directory problem (especially on
DKMS modules). He wrote:

> In Makefile, the ld flag `--thinlto-cache-dir' is set to
> `$(extmod_prefix).thinlto-cache'. But at that time, the variable extmod_prefix
> had not been assigned yet. Therefore, the thinlto cache dir is always created
> in the current directory.
> 
> Even worse, the cache dir cannot be deleted when executing `make clean'. This
> is because its path was written as `$(KBUILD_EXTMOD)/.thinlto-cache' in the
> clean: target.
> 
> Some users have been troubled by it: https://github.com/dell/dkms/issues/292
> 
> This bug was introduced by commit dc5723b02e523b2c4a68667f7e28c65018f7202f

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)