[PATCH v5 next 0/5] Improve Module autoloading infrastructure

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
2017-11-27 18:41:33
Also in
lkml, netdev
Reply to
Djalal Harouni, 2017-11-27
On Mon, Nov 27, 2017 at 9:18 AM, Djalal Harouni [off-list ref] wrote:
The sysctl flag is available at "/proc/sys/kernel/modules_autoload_mode"

When modules_autoload_mode is set to (0), the default, there are no
restrictions.
So quick question: do we actually need this?

Yes, it may be the current default, but is it anything that people
actually depend on?

I'd have expected that most module loading comes from system actions
anyway, not normal users.

So I'd like to explore first whether it even makes sense to make a new option.

New options are bad because:

 - opt-in security isn't security at all

 - having to configure things is complex

so we should generally strive to _not_ need new random config options.

What are the real life use-cases for normal users having modules auto-load?

               Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Thread (83 messages) 83 messages, 14 authors, last reply 2017-12-01
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help