Well the main argument of the article is that they physically fall apart quickly, and are difficult (or impossible without fabrication skills) to repair
if you read the mailing list, you know there’s a lot of reasons. Linus hates out of tree and closed modules for quite a number of reasons- but in this specific context it seems the most relevant.
You’re practically not supposed to to build external modules. It’s supported to only the most minimal degree- Linus, and the Linux project, WANT you to build things in.
And as everyone else has told you, this is so that support for hardware is in Linux and in distros BEFORE users have to taint their kernels and create crazy bugs kernel devs have to deal with.
EDIT: I just don’t trust promises for things to be open source. Notch said Minecraft would be open source, and look where that went. A promise let’s you skip out on releasing the code if it turns out to be a convenient or profitable options.
> System call filtering isn't a sandbox. It provides a clearly defined
mechanism for minimizing the exposed kernel surface. It is meant to be
a tool for sandbox developers to use. Beyond that, policy for logical
behavior and information flow should be managed with a combination of
other system hardening techniques and, potentially, an LSM of your
choosing