[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e3fbf778e64f4402b37c878dec580ba0@AcuMS.aculab.com>
Date: Tue, 26 Jan 2021 12:16:08 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Masahiro Yamada' <masahiroy@...nel.org>,
Kees Cook <keescook@...omium.org>
CC: Josh Poimboeuf <jpoimboe@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Michal Marek <michal.lkml@...kovi.net>,
"linux-hardening@...r.kernel.org" <linux-hardening@...r.kernel.org>,
"Linux Kbuild mailing list" <linux-kbuild@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Justin Forbes <jforbes@...hat.com>,
Ondrej Mosnacek <omosnace@...hat.com>
Subject: RE: [PATCH RFC] gcc-plugins: Handle GCC version mismatch for OOT
modules
> We started with the assumption that modules must be compiled
> by the same compiler as the kernel was.
> https://lore.kernel.org/patchwork/patch/836247/#1031547
>
> Now that the compiler capability is evaluated in Kconfig,
> this is a harder requirement.
>
> In reality, a different compiler might be used,
> and, this requirement might be loosened, but
> the same compiler should be required for CONFIG_GCC_PLUGINS.
Hmmmm.
If I'm building a module to load into a distro kernel
it is very unlikely that I'll actually have the same version
of the compiler installed as that used to build the kernel.
Additionally some of the .o files (that don't refer to any
kernel headers) may have been compiled with an entirely
different compiler altogether.
Whether any plugins are actually installed is another problem.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists