[lkml]   [2017]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v5 next 0/5] Improve Module autoloading infrastructure
On Mon, Nov 27, 2017 at 10:41 AM, Linus Torvalds
<> wrote:
> What are the real life use-cases for normal users having modules auto-load?

Well, I could do some testing. One case is apparently both bluetoothd
and ip6tables that have been converted to indeed use CAP_NET_ADMIN.


Still, can't we just say "you need to have capabilities" and leave it at that?

Something (UNTESTED and whitespace damaged) like this:

diff --git a/kernel/kmod.c b/kernel/kmod.c
index bc6addd9152b..a3f3218f66c6 100644
--- a/kernel/kmod.c
+++ b/kernel/kmod.c
@@ -139,6 +139,11 @@ int __request_module(bool wait, const char *fmt, ...)
if (!modprobe_path[0])
return 0;

+ if (WARN_ON_ONCE(!capable(CAP_SYS_MODULE) ||
+ !capable(CAP_SYS_ADMIN) ||
+ !capable(CAP_NET_ADMIN)))
+ return -EPERM;
va_start(args, fmt);
ret = vsnprintf(module_name, MODULE_NAME_LEN, fmt, args);

instead of adding complex infrastructure for something people might
not want anyway?

Now, the above will not necessarily work with a legacy /dev/ directory
where al the nodes have been pre-populated, and opening the device
node is supposed to load the module. So _historically_ we did indeed
load modules as normal users. But does that really happen any more?

I'd hate to default to historical behavior if there's no actual reason to do so.


 \ /
  Last update: 2017-11-27 20:03    [W:0.167 / U:3.432 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site