Re: valid module function pointer?

Alan Cox (alan@lxorguk.ukuu.org.uk)
Fri, 17 Sep 1999 23:24:52 +0100 (BST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Dipl.-Ing. Uwe Koloska: "Re: bug in socket.h (and maybe many other kernel headerfiles)"
Previous message: Dave: "Re: Ext3 filesystem info?"
In reply to: Jamie Lokier: "Re: sigwaitinfo(), close(), siginfo_t, and user data"
Next in thread: Richard Guy Briggs: "Re: linux-ipsec: Re: valid module function pointer?"
Reply: Richard Guy Briggs: "Re: linux-ipsec: Re: valid module function pointer?"

> Can anyone suggest a way to test a module function pointer for
> validity? The problem is that we currently save pointers to kernel
> space funciton pointers which might go away if a pcmcia card is
> removed. Is there a way to test if the function pointer belongs to a
> module which is still loaded?

No. You need to ensure it isnt unloaded on you. Look at the network device
notifier

-
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/

Next message: Dipl.-Ing. Uwe Koloska: "Re: bug in socket.h (and maybe many other kernel headerfiles)"
Previous message: Dave: "Re: Ext3 filesystem info?"
In reply to: Jamie Lokier: "Re: sigwaitinfo(), close(), siginfo_t, and user data"
Next in thread: Richard Guy Briggs: "Re: linux-ipsec: Re: valid module function pointer?"
Reply: Richard Guy Briggs: "Re: linux-ipsec: Re: valid module function pointer?"