Linus and the rest of the Linux kernel developers make it intentionally hard to keep out-of-tree modules working against the kernel for the same reason that GCC does, which is to have the code included into the main project where it will benefit all end users instead of having proprietary/out-of-tree modules/plugins which are available to a select audience.
I can't see how you can claim that Linus stands 'directly against this sort of idea'. They seem very much aligned to me.
That's a different problem - namely that they don't want to tie Linux to having a stable ABI.
The side-effect is that it makes it difficult to maintain out-of-tree modules, because people don't fix things as they edit the kernel (if it builds, it builds etc.)
No they are deliberately adding GPLONLY symbol restrictions to prevent proprietary linking with the kernel, which has nothing to do with keeping a stable ABI.
They can keep the ABI as unstable as they want while still allowing proprietary linking, they don't have to provide any maintenance help to proprietary vendors who wants to link to the kernel.
Linus and the rest of the Linux kernel developers make it intentionally hard to keep out-of-tree modules working against the kernel for the same reason that GCC does, which is to have the code included into the main project where it will benefit all end users instead of having proprietary/out-of-tree modules/plugins which are available to a select audience.
I can't see how you can claim that Linus stands 'directly against this sort of idea'. They seem very much aligned to me.