Jan Engelhardt wrote:
On Dec 15 2007 17:42, Pablo Neira Ayuso wrote:
Netlink doesn't stick us to fixed structure layouts as it happens to the
current interface since we represent the messages kernel <-> userspace
in TLV (type-length-value) format. Thus, userspace and kernel won't
share structures and new features just require a new type. For that
reason, the netlink interface won't require such revision infrastructure.
Please explain the TLV thing. How would something like
struct ipt_tos_target_info (revision 0, in net-2.6.25/xt_DSCP.c) and
struct xt_tos_target_info (revision 1, in net-2.6.25/xt_DSCP.c) be
encoded?
Does the mere presence of a TLV block (sending it over netlink) indicate
a certain revision?
Since the kernel doesn't share structures with userspace anymore,
you can simply use the most generic form within the kernel and
put the userspace-data in the required form during initialization.
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
