David Howells wrote:
>
> Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de> wrote:
> > I see two possible solutions.
> >
> > Either you make that function available to user space by your syscall.
>
> Not a good idea... the whole point is to make sure no one is in a syscall when
> the module is unloaded. If you do it this way, the tail end of this syscall
> can fight with the module unload code.
>
> > Or you find a way to hook into task termination.
>
> I'm already doing that... See the release() call on the fd. But this doesn't
> stop someone from invoking a syscall at an inappropriate time.
>
> David Howells
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
The best solution is to have a stub which is always resident that does
the inc/dec of the module count. This stub can reserve the syscall
number as well.
--Brian Gerst - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:15 EST