Skip to contentSkip to conversation

rmmod & O_NONBLOCK: why to block?

DISCUSSION Michael Tokarev 1 participant 1 message Dec 22, 2004

lore
Share & tools
lore
#0 lore raw

With "new" (not so new anymore) module infrastructure, the caller -- in delete_module() syscall -- may specify O_NONBLOCK to indicate it is not willing to wait for the module refcount to become 0 -- IF I understand this flag correctly.

Yet it is not really honored by the kernel, kernel places the process who issued remove_module() call into uninterruptable state.

Current rmmod from module-init-tools first checks whenever the use count is zero, and if it is, tries to remove the module (not that simple, there's also forced unload etc, but basically that's it). But it's trivial to have a race
here: when we looked for refcount, it was zero, but when we're trying to do actual remove, it is not anymore: rmmod will block, even without -w flag.

Here's the relevant code from kernel/module.c, "simplified" a bit for better readability:

int try_stop_module(mod, flags) {
foreach_cpu() { // actually stop_machine_run()

      /* If it's not unused, quit unless we are told to block. */
      if ((flags & O_NONBLOCK) && module_refcount(mod) != 0) {
         if (!try_force(flags))
           return -EWOULDBLOCK;
      }

}
return 0;
}

long sys_delete_module(module, flags) {
        ...
        /* Set this up before setting mod->state */
        mod->waiter = current;

        /* Stop the machine so refcounts can't move and disable module. */
        ret = try_stop_module(mod, flags, &forced);

        /* Never wait if forced. */
        if (!forced && module_refcount(mod) != 0)
                wait_for_zero_refcount(mod);

        free_module(mod);
        return ret;
}

In short, try_stop_module() can return -EWOULDBLOCK (or stop_machine_run() may fail for other reasons too), but the return value is never checked... Should there be an "if (ret != 0) return ret;" somewhere right after try_stop_module() call? But since I don't quite understand all the logic here, I don't know what to do with mod->waiter assigned in the previous line.

(And, I'm not sure stop_machine_run() returns whatever result actual routine returned, -EWOULDBLOCK in this case).

BTW, why this wait_for_zero_refcount() at all? Why/where/how it can be useful? It's relatively easy to implement in userspace with try/sleep loop, but having unkillable processes in wait_for_zero_refcount state isn't good...

Comments anyone?

/mjt