Denis V. Lunev cd40b7d398 [NET]: make netlink user -> kernel interface synchronious ... This patch make processing netlink user -> kernel messages synchronious. This change was inspired by the talk with Alexey Kuznetsov about current netlink messages processing. He says that he was badly wrong when introduced asynchronious user -> kernel communication. The call netlink_unicast is the only path to send message to the kernel netlink socket. But, unfortunately, it is also used to send data to the user. Before this change the user message has been attached to the socket queue and sk->sk_data_ready was called. The process has been blocked until all pending messages were processed. The bad thing is that this processing may occur in the arbitrary process context. This patch changes nlk->data_ready callback to get 1 skb and force packet processing right in the netlink_unicast. Kernel -> user path in netlink_unicast remains untouched. EINTR processing for in netlink_run_queue was changed. It forces rtnl_lock drop, but the process remains in the cycle until the message will be fully processed. So, there is no need to use this kludges now. Signed-off-by: Denis V. Lunev <den@openvz.org> Acked-by: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru> Signed-off-by: David S. Miller <davem@davemloft.net>		2007-10-10 21:15:29 -07:00
..
crypto.c
debug.c
dentry.c
ecryptfs_kernel.h
file.c
inode.c
keystore.c
main.c
Makefile
messaging.c
mmap.c	eCryptfs: fix possible fault in ecryptfs_sync_page	2007-08-31 01:42:23 -07:00
netlink.c	[NET]: make netlink user -> kernel interface synchronious	2007-10-10 21:15:29 -07:00
super.c