> Not being able to unload LSM would suck enormously. At last count, we
> knew how to do this:
>
> 1) Unhook the function hooks (using a call table simplifies this)
> 2) Schedule on each CPU to ensure all tasks are out of the module
> 3) A schedule where the module count is incremented doesn't count
>
> and we rely on the rule that and module code that could sleep must be
> bracketed by inc/dec of the module count.
>
> Did somebody come up with a reason why this will not work?
Preemption?
Scheduling doesn't guarantee making any specific amount of progress within
the kernel with preemption enabled. I thought the preferred strategy was to
wait for the time slices to refill and then exhaust (since everybody has to
exhaust their time slices before anybody gets new ones. Unless I've missed
something...?)
Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/