Seems to me that module _replacement_ (as opposed to
unloading in order to free memory) is an easier case.
Just load the new module and initialize it. If some
other preempted processor manages to race and activate
the old module - no problem, because the code isn't gone.
The old module may be unloaded once we know the new one
will get all future requests and the old one has 0 references.
Helge Hafting
-
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/