Received-SPF: pass (google.com: domain of linux-kernel+bounces-176502-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Sat, 11 May 2024 18:18:38 +0700
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kernel Build System <linux-kbuild@vger.kernel.org>
Cc: Sami Tolvanen <samitolvanen@google.com>,
	Kees Cook <keescook@chromium.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Xu Zhen <xuzhen@fastmail.com>
Subject: Fwd: Incorrect thinlto cache directory path in Makefile
Message-ID: <Zj9UDiAHqX3noTsy@archie.me>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="hvHleVGfPEbZBFqD"
Content-Disposition: inline


--hvHleVGfPEbZBFqD
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

Xu Zhen <xuzhen@fastmail.com> reported on Bugzilla (https://bugzilla.kernel=
=2Eorg/show_bug.cgi?id=3D218825) thinlto build directory problem (especiall=
y 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_p=
refix
> had not been assigned yet. Therefore, the thinlto cache dir is always cre=
ated
> in the current directory.
>=20
> 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 t=
he
> clean: target.
>=20
> Some users have been troubled by it: https://github.com/dell/dkms/issues/=
292
>=20
> This bug was introduced by commit dc5723b02e523b2c4a68667f7e28c65018f7202f

Thanks.

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

--hvHleVGfPEbZBFqD
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZj9UCAAKCRD2uYlJVVFO
o+joAQDEeSJZ9MQqSgMq9VrowDQyslrDGOS3Ao0Ams995iBjWwEAoFLnO3v6bpB1
Ij3UAqQrVp443gHQVkZh7BnktFni0gU=
=+Bm5
-----END PGP SIGNATURE-----

--hvHleVGfPEbZBFqD--