@@ -1858,7 +1858,7 @@ unloaded. After a given module has been
one of its functions results in a segmentation fault. The module-unload
functions must therefore cancel any delayed calls to loadable-module
functions, for example, any outstanding mod_timer() must be dealt
-with via timer_delete_sync() or similar.
+with via timer_shutdown_sync() or similar.
Unfortunately, there is no way to cancel an RCU callback; once you
invoke call_rcu(), the callback function is eventually going to be
@@ -191,7 +191,7 @@ Here is a sample module which implements
static void __exit test_exit(void)
{
- timer_delete_sync(&test_timer);
+ timer_shutdown_sync(&test_timer);
}
module_init(test_init);
@@ -1007,6 +1007,11 @@ calling add_timer() at the end of their
Because this is a fairly common case which is prone to races, you should
use timer_delete_sync() (``include/linux/timer.h``) to handle this case.
+Before freeing a timer, timer_shutdown() or timer_shutdown_sync() should be
+called which will keep it from being rearmed. Any subsequent attempt to
+rearm the timer will be silently ignored by the core code.
+
+
Locking Speed
=============
@@ -185,7 +185,7 @@ UP之间没有不同的行为，在你�
static void __exit test_exit(void)
{
- timer_delete_sync(&test_timer);
+ timer_shutdown_sync(&test_timer);
}
module_init(test_init);