[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210127180324.GB1745339@infradead.org>
Date: Wed, 27 Jan 2021 18:03:24 +0000
From: Christoph Hellwig <hch@...radead.org>
To: Justin Forbes <jforbes@...hat.com>
Cc: Greg KH <greg@...ah.com>, Josh Poimboeuf <jpoimboe@...hat.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Kees Cook <keescook@...omium.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Michal Marek <michal.lkml@...kovi.net>,
linux-hardening@...r.kernel.org,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ondrej Mosnacek <omosnace@...hat.com>
Subject: Re: [PATCH RFC] gcc-plugins: Handle GCC version mismatch for OOT
modules
On Tue, Jan 26, 2021 at 06:44:44AM -0600, Justin Forbes wrote:
> Support and enforce are 2 completely different things. To shed a bit
> more light on this, the real issue that prompted this was breaking CI
> systems. As we enabled gcc plugins in Fedora, and the toolchain folks
> went through 3 different snapshots of gcc 11 in a week. Any CI process
> that built an out of tree module failed. I don't think this is nearly
> as much of a concern for stable distros, as it is for CI in
> development cycles.
And the answer is trivial: don't build out of tree modules.
Powered by blists - more mailing lists