Thanks Mark, I am using 2.6.26 kernel. Can you please explain, why you specifically mentioned the kernel 2.6.24 or below? What is difference between 2.6.24 kernel and latest kernel in this regards?
Thanks and Regards, Prasad On Mon, Aug 4, 2008 at 1:03 AM, Mark Brown <[EMAIL PROTECTED]>wrote: > If you are using kernel 2.6.24 or below you can specify the prototype: > > extern int get_filesystem_list(char *); > > It does not look like this function was intended for general use, so be > careful. > > Regards, > -- Mark > > > On Aug 3, 2008, at 1:04 PM, Rene Herman wrote: > > On 03-08-08 17:44, Prasad Joshi wrote: >> >> I am calling a function get_filesystem_list() from a module which I am >>> writing. During the compilation I am getting the error >>> WARNING: get_filesystem_list [module name] undefined! >>> And the insertion of the module also fails giving error unresolved >>> symbol. >>> I need the list of file systems registered on the system, >>> get_filesystem_list() does the same. >>> I have included the file <linux/fs.h> as well. Why is it not working and >>> how to make it work? >>> >> >> get_filesystem_list() is not exported for use by modules. Probably just >> because noone needs it... >> >> For your own personal use, you can just export if from your kernel >> yourself. Add a >> >> EXPORT_SYMBOL(get_filesystem_list); >> >> directly after the closing brace of get_filesystem_list() (that location >> is just convention, technically anywhere would be fine) and recmpile the >> kernel. After reboot, get_filesystem_list() is available to modules. >> >> Rene. >> >> -- >> To unsubscribe from this list: send an email with >> "unsubscribe kernelnewbies" to [EMAIL PROTECTED] >> Please read the FAQ at http://kernelnewbies.org/FAQ >> >> >
