linux/include/net/netlink.h, branch v3.8

netlink: Rename pid to portid to avoid confusion

2012-09-10T19:30:41Z

It is a frequent mistake to confuse the netlink port identifier with a process identifier. Try to reduce this confusion by renaming fields that hold port identifiers portid instead of pid. I have carefully avoided changing the structures exported to userspace to avoid changing the userspace API. I have successfully built an allyesconfig kernel with this change. Signed-off-by: "Eric W. Biederman" Acked-by: Stephen Hemminger Signed-off-by: David S. Miller

netlink: add signed types

2012-08-04T03:40:11Z

Signed types might be needed in NL communication from time to time (I need s32 in team driver), so add them. Signed-off-by: Jiri Pirko Signed-off-by: David S. Miller

netlink: Delete all NLA_PUT*() macros.

2012-04-02T08:33:45Z

They were error prone due to an embedded goto, and the entire tree has been converted away from using them. Signed-off-by: David S. Miller

netlink: Add nla_put_le{16,32,64}() helpers.

2012-04-02T08:33:42Z

Signed-off-by: David S. Miller

netlink: Add nla_put_net{16,32,64}() helpers.

2012-04-02T08:33:41Z

Signed-off-by: David S. Miller

netlink: Add nla_put_be{16,32,64}() helpers.

2012-04-01T22:11:37Z

Signed-off-by: David S. Miller

net: Deinline __nlmsg_put and genlmsg_put. -7k code on i386 defconfig.

2012-01-30T20:22:06Z

text data bss dec hex filename 8455963 532732 1810804 10799499 a4c98b vmlinux.o.before 8448899 532732 1810804 10792435 a4adf3 vmlinux.o This change also removes commented-out copy of __nlmsg_put which was last touched in 2005 with "Enable once all users have been converted" comment on top. Changes in v2: rediffed against net-next. Signed-off-by: Denys Vlasenko Signed-off-by: David S. Miller

netlink: clarify attribute length check documentation

2011-11-04T21:48:23Z

The documentation for how the length of attributes is checked is wrong ("Exact length" isn't true, the policy checks are for "minimum length") and a bit misleading. Make it more complete and explain what really happens. Cc: Thomas Graf Signed-off-by: Johannes Berg Signed-off-by: David S. Miller

netlink: advertise incomplete dumps

2011-06-22T20:09:45Z

Consider the following situation: * a dump that would show 8 entries, four in the first round, and four in the second * between the first and second rounds, 6 entries are removed * now the second round will not show any entry, and even if there is a sequence/generation counter the application will not know To solve this problem, add a new flag NLM_F_DUMP_INTR to the netlink header that indicates the dump wasn't consistent, this flag can also be set on the MSG_DONE message that terminates the dump, and as such above situation can be detected. To achieve this, add a sequence counter to the netlink callback struct. Of course, netlink code still needs to use this new functionality. The correct way to do that is to always set cb->seq when a dumpit callback is invoked and call nl_dump_check_consistent() for each new message. The core code will also call this function for the final MSG_DONE message. To make it usable with generic netlink, a new function genlmsg_nlhdr() is needed to obtain the netlink header from the genetlink user header. Signed-off-by: Johannes Berg Acked-by: David S. Miller Signed-off-by: John W. Linville

treewide: fix a few typos in comments

2011-05-10T08:16:21Z

- kenrel -> kernel - whetehr -> whether - ttt -> tt - sss -> ss Signed-off-by: Justin P. Mattock Signed-off-by: Jiri Kosina