|> I've just run into some problems while writing a proc-entry. The problem is
|> inconsistency in function pointer 'types'. I did as Luke, I used the source and
|> found something odd.
|> In include/linux/fs.h the file_operations struct defines a read function as
|> follows:
|> struct file_operations {
|> ...
|> ssize_t (*read) (struct file *, char *, size_t, loff_t *);
|> ...
|> };
|> In fs/proc/net.c this read-function pointer gets the address of the following
|> function (also located in fs/proc/net.c):
|> static long proc_readnet(struct inode * inode, struct file * file,
|> char * buf, unsigned long count)
fs/proc/net.c is obsolete and unused. It should probably be removed.
-- Andreas Schwab "And now for something schwab@issan.informatik.uni-dortmund.de completely different" schwab@gnu.org- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu