On Tue, Mar 6, 2018 at 12:01 PM, Andy Lutomirski <l...@kernel.org> wrote: > > I assume I'm missing some context here, but why does this need to be > handled by the kernel rather than, say, a change to how modprobe > works?
Honestly, the less we have to mess with user-mode tooling, the better. We've been *so* much better off moving most of the module loading logic to the kernel, we should not go back in the old broken direction. I do *not* want the kmod project that is then taken over by systemd, and breaks it the same way they broke firmware loading. Keep modprobe doing one thing, and one thing only: track dependencies and mindlessly just load the modules. Do *not* ask for it to do anything else. Right now kmod is a nice simple project. Lots of testsuite stuff, and a very clear goal. Let's keep kmod doing one thing, and not even have to care about internal kernel decisions like "oh, this module might not be a module, but an executable". If anything, I think we want to keep our options open, in the case we need or want to ever consider short-circuiting things and allowing direct loading of the simple cases and bypassing modprobe entirely. Linus