Doh I'd been looking at filp_open without realising the lock is already held.
> sys_delete_module() does
>
> lock_kernel()
> Test module in use.
> free_module()
> unlock_kernel()
>
> AFAICT, both the module open routine and the module unloading code run
> under the big kernel lock, no races are possible.
Agreed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/