linux-kernel - netlink: symantics for NLM_F_MULTI and NLMSG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1256584493.10998.784.camel@montana.filmlight.ltd.uk>
Date:	Mon, 26 Oct 2009 19:14:53 +0000
From:	Roger Willcocks <roger@...mlight.ltd.uk>
To:	linux-kernel@...r.kernel.org
Subject: netlink: symantics for NLM_F_MULTI and NLMSG_DONE ?

The netlink rfc (3549) says that in multi-part messages (messages split
over multiple netlink packets), the first and all following headers 
have the NLM_F_MULTI flag set except for the last header which has the
header type NLMSG_DONE.

afaict NLMSG_DONE is redundant, since one could simply not set the
NLM_F_MULTI flag for the final header; and if a multi-part message
can't cross a datagram boundary - which is assumed by e.g. the reading
example in
http://www.kernel.org/doc/man-pages/online/pages/man7/netlink.7.html
- NLMSG_DONE is redundant too.

And the rfc doesn't say what NLMSG_DONE /and/ NLM_F_MULTI should mean,
although net/netlink/af_netlink.c always sets both.

So, what are the symantics for NLM_F_MULTI and NLMSG_DONE?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/