linux-toradex.git/include/linux/netlink.h, branch v2.6.18-rc7

[PATCH] w1: netlink: Mark netlink group 1 as unused.

2006-06-22T18:22:50+00:00

netlink_w1 was moved to connector.

Signed-off-by: Evgeniy Polyakov 
Signed-off-by: Greg Kroah-Hartman

[PATCH] Reworked patch for labels on user space messages

2006-05-01T10:09:58+00:00

The below patch should be applied after the inode and ipc sid patches.
This patch is a reworking of Tim's patch that has been updated to match
the inode and ipc patches since its similar.

[updated:
>  Stephen Smalley also wanted to change a variable from isec to tsec in the
>  user sid patch.                                                              ]

Signed-off-by: Steve Grubb 
Signed-off-by: Al Viro

[NETLINK]: Add netlink_has_listeners for avoiding unneccessary event message generation

2006-03-21T02:52:01+00:00

Keep a bitmask of multicast groups with subscribed listeners to let
netlink users check for listeners before generating multicast
messages.

Queries don't perform any locking, which may result in false
positives, it is guaranteed however that any new subscriptions are
visible before bind() or setsockopt() return.

Signed-off-by: Patrick McHardy 
ACKed-by: Jamal Hadi Salim
Signed-off-by: David S. Miller

[NETLINK]: Fix a severe bug

2006-02-10T00:43:38+00:00

netlink overrun was broken while improvement of netlink.
Destination socket is used in the place where it was meant to be source socket,
so that now overrun is never sent to user netlink sockets, when it should be,
and it even can be set on kernel socket, which results in complete deadlock
of rtnetlink.

Suggested fix is to restore status quo passing source socket as additional
argument to netlink_attachskb().

A little explanation: overrun is set on a socket, when it failed
to receive some message and sender of this messages does not or even
have no way to handle this error. This happens in two cases:
1. when kernel sends something. Kernel never retransmits and cannot
   wait for buffer space.
2. when user sends a broadcast and the message was not delivered
   to some recipients.

Signed-off-by: Alexey Kuznetsov 
Signed-off-by: David S. Miller

[NETLINK]: Type-safe netlink messages/attributes interface

2005-11-10T01:26:40+00:00

Introduces a new type-safe interface for netlink message and
attributes handling. The interface is fully binary compatible
with the old interface towards userspace. Besides type safety,
this interface features attribute validation capabilities,
simplified message contstruction, and documentation.

The resulting netlink code should be smaller, less error prone
and easier to understand.

Signed-off-by: Thomas Graf 
Signed-off-by: David S. Miller

[PATCH] gfp flags annotations - part 1

2005-10-08T22:00:57+00:00

 - added typedef unsigned int __nocast gfp_t;

 - replaced __nocast uses for gfp flags with gfp_t - it gives exactly
   the same warnings as far as sparse is concerned, doesn't change
   generated code (from gcc point of view we replaced unsigned int with
   typedef) and documents what's going on far better.

Signed-off-by: Al Viro 
Signed-off-by: Linus Torvalds

[NETLINK]: Reserve a slot for NETLINK_GENERIC.

2005-09-15T03:52:37+00:00

As requested by Jamal.

Signed-off-by: David S. Miller

[NET]: Add netlink connector.

2005-09-12T02:15:07+00:00

Kernel connector - new userspace <-> kernel space easy to use
communication module which implements easy to use bidirectional
message bus using netlink as it's backend.  Connector was created to
eliminate complex skb handling both in send and receive message bus
direction.

Connector driver adds possibility to connect various agents using as
one of it's backends netlink based network.  One must register
callback and identifier. When driver receives special netlink message
with appropriate identifier, appropriate callback will be called.

From the userspace point of view it's quite straightforward:

	socket();
	bind();
	send();
	recv();

But if kernelspace want to use full power of such connections, driver
writer must create special sockets, must know about struct sk_buff
handling...  Connector allows any kernelspace agents to use netlink
based networking for inter-process communication in a significantly
easier way:

int cn_add_callback(struct cb_id *id, char *name, void (*callback) (void *));
void cn_netlink_send(struct cn_msg *msg, u32 __groups, int gfp_mask);

struct cb_id
{
	__u32			idx;
	__u32			val;
};

idx and val are unique identifiers which must be registered in
connector.h for in-kernel usage.  void (*callback) (void *) - is a
callback function which will be called when message with above idx.val
will be received by connector core.

Using connector completely hides low-level transport layer from it's
users.

Connector uses new netlink ability to have many groups in one socket.

[ Incorporating many cleanups and fixes by myself and
  Andrew Morton -DaveM ]

Signed-off-by: Evgeniy Polyakov 
Signed-off-by: Andrew Morton 
Signed-off-by: David S. Miller

[NETLINK]: Fix sparse warnings

2005-08-29T23:01:35+00:00

Signed-off-by: Arnaldo Carvalho de Melo 
Signed-off-by: David S. Miller

[NETLINK]: Add "groups" argument to netlink_kernel_create

2005-08-29T23:01:11+00:00

Signed-off-by: Patrick McHardy 
Signed-off-by: David S. Miller