SysVIPC is irrelevant to kmod. It was used for kerneld and the
problems it caused was one of the reasons that kerneld was replaced
with kmod. To rephrase your question - why not disallow Unix domain
sockets as a module when kmod is enabled?
(a) People want to have Unix sockets as modules. No idea why but they
do. Enough people have tripped over this loop using module sockets
to make it worthwhile pacthing it.
(b) The kmod/module loop caused by syslog() is not the only possible
loop, just the most common. I wanted a general fix.
(c) Forbidding one combination only works until the next kernel change
that trips this problem. A general fix is better.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/