[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171128.041426.801732093971324601.davem@davemloft.net>
Date: Tue, 28 Nov 2017 04:14:26 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: torvalds@...ux-foundation.org
Cc: tixxdz@...il.com, keescook@...omium.org, luto@...nel.org,
akpm@...ux-foundation.org, mcgrof@...nel.org,
james.l.morris@...cle.com, ben.hutchings@...ethink.co.uk,
solar@...nwall.com, serge@...lyn.com, jeyu@...nel.org,
rusty@...tcorp.com.au, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
kernel-hardening@...ts.openwall.com, corbet@....net,
mingo@...nel.org, netdev@...r.kernel.org, peterz@...radead.org
Subject: Re: [PATCH v5 next 0/5] Improve Module autoloading infrastructure
From: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Mon, 27 Nov 2017 10:41:30 -0800
> What are the real life use-cases for normal users having modules
> auto-load?
User opens SCTP socket, SCTP protocol module loads.
People build test cases via namespaces, and in that namespaces normal
users can setup virtual tunnel devices themselves, and those configure
operations can bring the tunnel module in.
Powered by blists - more mailing lists