[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210127184327.GA1755516@infradead.org>
Date: Wed, 27 Jan 2021 18:43:27 +0000
From: Christoph Hellwig <hch@...radead.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Kees Cook <keescook@...omium.org>,
linux-kernel@...r.kernel.org,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
linux-hardening@...r.kernel.org, linux-kbuild@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Justin Forbes <jforbes@...hat.com>,
Ondrej Mosnacek <omosnace@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH RFC] gcc-plugins: Handle GCC version mismatch for OOT
modules
On Wed, Jan 27, 2021 at 12:38:56PM -0600, Josh Poimboeuf wrote:
> On Wed, Jan 27, 2021 at 06:02:15PM +0000, Christoph Hellwig wrote:
> > Please don't add all this garbage. We only add infrastructure to the
> > kernel for what the kernel itself needs, not for weird out of tree
> > infrastructure.
>
> This isn't new, the kernel already has the infrastructure for building
> out-of-tree modules. It's widely used. Are you suggesting we remove
> it? Good luck with that...
>
> Either it should be supported, or not. Make the case either way. But I
> can't understand why people are advocating to leave it half-broken.
It is not support as any kind of interface. It is a little aid for
local development. Adding any kond of complexities for out of tree
modules is a complete no-go.
Powered by blists - more mailing lists