Netlink sockets usage to communicate b/w user and kernel space.
While creating a netlink socket in the Kernel space i read in a website lwn.net/Articles/131802/ that, if the second argument to
struct sock *netlink_kernel_create(int unit,
void (*input)(struct sock *sk, int len)); is NULL, that is, if the call back function to handle is NULL, user space cannot write a message to the socket.
Is this right??
My requirement is i need to send a message from user space to kernel space. But, i don't want any callback function to handle the message received from the netlink socket. So i have specified the second argument in netlink_kernel_create as NULL. But after reading the article in the site, i think i should re-write some part of the code.
Kindly tell me whether it is mandatory to mention a function pointer as second argument if i want to send a message from user to kernel space by writing in the socket created.