API changes
RFC 3/3 API changes
This patch introduces the following changes:
a) nfnl_handle_msg: this function completes the message iterator API.
nlh = nfnl_get_first_msg(h, ...);
while (nlh) {
int done;
...
ret = nfnl_handle_msg(h, &done);
if (ret < 0 || done)
return ret;
nlh = nfnl_get_next_msg(h, ...);
}Like this, we can iterate over the netlink messages that compose a packet. The message is processed by nfnl_handle_msg that calls the handler that was registered via nfnl_callback_register.
The done flag is set to one if the message is:
- an ACK/ERROR message
- a DONE message that notifies the end of a MULTI message.
b) nfnl_handle_packet: This function is simpler interface to handle a netfilter netlink message. It loops over every message contained in a packet but, in this case, the programmer has no control on the looping process. Moreover, this function now has a done flag that is set under the same circunstances exposed above.
c) nfnl_communicate: This function supersedes nfnl_listen and nfnl_talk. It provides an interface to communicate with the nfnetlink subsystem.
- If the netlink header passed is null and a handler is registered via nfnl_callback_register, then it behaves like nfnl_listen.
- If the netlink header passed is non-null and no handler was registered via nfnl_callback_register, then it behaves like nfnl_talk.
Signature · 1 line
Pablo
This patch introduces the following changes:
a) nfnl_handle_msg: this function completes the message iterator API.
nlh = nfnl_get_first_msg(h, ...);
while (nlh) {
int done;
...
ret = nfnl_handle_msg(h, &done);
if (ret < 0 || done)
return ret;
nlh = nfnl_get_next_msg(h, ...);
}Like this, we can iterate over the netlink messages that compose a packet. The message is processed by nfnl_handle_msg that calls the handler that was registered via nfnl_callback_register.
The done flag is set to one if the message is:
- an ACK/ERROR message
- a DONE message that notifies the end of a MULTI message.
b) nfnl_handle_packet: This function is simpler interface to handle a netfilter netlink message. It loops over every message contained in a packet but, in this case, the programmer has no control on the looping process. Moreover, this function now has a done flag that is set under the same circunstances exposed above.
c) nfnl_communicate: This function supersedes nfnl_listen and nfnl_talk. It provides an interface to communicate with the nfnetlink subsystem.
- If the netlink header passed is null and a handler is registered via nfnl_callback_register, then it behaves like nfnl_listen.
- If the netlink header passed is non-null and no handler was registered via nfnl_callback_register, then it behaves like nfnl_talk.
src/libnfnetlink.c +63 -4
@@ -969,17 +969,28 @@ static int __nfnl_handle_msg(struct nfnlreturn 0 ; } -int nfnl_handle_packet (struct nfnl_handle *h,char *buf,int len) +int nfnl_handle_packet (struct nfnl_handle *h,char *buf,int len,int *done) { +struct nlmsghdr *nlh = (struct nlmsghdr *)buf; -while (len >=NLMSG_SPACE (0 )) { +while (NLMSG_OK (nlh, len)) {u_int32_t rlen; -struct nlmsghdr *nlh = (struct nlmsghdr *)buf;if (nlh->nlmsg_len <sizeof (struct nlmsghdr ) || len < nlh->nlmsg_len)return -1 ; +/* This message is an ACK or a DONE */ +if (done && + (nlh->nlmsg_type ==NLMSG_ERROR || + (nlh->nlmsg_type ==NLMSG_DONE && + nlh->nlmsg_flags &NLM_F_MULTI ))) { +int err; + *done =1 ; +memcpy (&err,NLMSG_DATA (nlh),sizeof (int )); +return err; + } + rlen =NLMSG_ALIGN (nlh->nlmsg_len);if (rlen > len) rlen = len;
@@ -987,7 +998,55 @@ int nfnl_handle_packet(struct nfnl_handlif (__nfnl_handle_msg (h, nlh, rlen) <0 )return -1 ; - len -= rlen; + nlh =NLMSG_NEXT (nlh, len); }return 0 ; } + +int nfnl_handle_msg (struct nfnl_handle *h,int *done) +{ +int err =0 ; + +if (h->last_nlhdr->nlmsg_len >=NLMSG_SPACE (0 )) { +int len =NLMSG_ALIGN (h->last_nlhdr->nlmsg_len); + +if (h->last_nlhdr->nlmsg_len <sizeof (struct nlmsghdr ) + || len < h->last_nlhdr->nlmsg_len) +return -1 ; + +/* This message is an ACK or a DONE */ +if (done && (h->last_nlhdr->nlmsg_type ==NLMSG_ERROR || + (h->last_nlhdr->nlmsg_type ==NLMSG_DONE && + h->last_nlhdr->nlmsg_flags &NLM_F_MULTI ))) { + *done =1 ; +memcpy (&err,NLMSG_DATA (h->last_nlhdr),sizeof (int )); +return err; + } + + err =__nfnl_handle_msg (h, h->last_nlhdr, len); + } +return err; +} + +int nfnl_communicate (struct nfnl_handle *h,struct nlmsghdr *nlh) +{ +int ret, numbytes, done =0 ; +char buf[NFNL_BUFFSIZE ]; + +if (nlh) { + ret =nfnl_send (h, nlh); +if (ret <0 ) +return ret; + } + +while (1 ) { + numbytes =nfnl_recv (h, buf,sizeof (buf)); +if (numbytes <=0 ) +return numbytes; + + ret =nfnl_handle_packet (h, buf, numbytes, &done); +if (ret <0 || done) +return ret; + } +return ret; +}
include/libnfnetlink/libnfnetlink.h +3 -1
@@ -71,6 +71,7 @@ extern int nfnl_talk(struct nfnl_handle unsigned, struct nlmsghdr *, int (*)(struct sockaddr_nl *, struct nlmsghdr *, void *), void *); +extern int nfnl_communicate (struct nfnl_handle *h,struct nlmsghdr *nlh);/* simple challenge/response */ extern int nfnl_listen(struct nfnl_handle *,
@@ -82,7 +83,8 @@ extern ssize_t nfnl_recv(const struct nfextern int nfnl_callback_register (struct nfnl_subsys_handle *,u_int8_t type,struct nfnl_callback *cb);extern int nfnl_callback_unregister (struct nfnl_subsys_handle *,u_int8_t type); -extern int nfnl_handle_packet (struct nfnl_handle *,char *buf,int len); +extern int nfnl_handle_packet (struct nfnl_handle *,char *buf,int len,int *); +extern int nfnl_handle_msg (struct nfnl_handle *h,int *done);/* parsing */ extern struct nfattr *nfnl_parse_hdr(const struct nfnl_handle *nfnlh,
Quoted 3 lines · Pablo Neira Ayuso
This patch introduces the following changes:
a)
nfnl_handle_msg: this function completes the message iterator API.
looks nice to me.
Quoted 5 lines
b)
nfnl_handle_packet: This function is simpler interface to handle a netfilter netlink message. It loops over every message contained in a packet but, in this case, the programmer has no control on the looping process. Moreover, this function now has a done flag that is set under the same circunstances exposed above.
this change looks also fine to me, but since it changes an existing function, it introduces library incompatibility between the users (libnetfilter_*) and libnfnetlink.
Quoted 2 lines
c)
nfnl_communicate: This function supersedesnfnl_listenandnfnl_talk. It provides an interface to communicate with the nfnetlink subsystem.
also sound reasonable.
So how do we proceed?
I think at the moment, a new release of [most of] the libraries is needed due to accumulated bugfixes anyway. So I'd rather make a maintainance release with what we've got now than to introduce API changes. Addidional API (nfnl_communicate, nfnl_handle_msg) is not a problem at all.
As for the only API change (nfnl_handle_packet), I would like to know if there is an urgent need for the 'done' flag in any of the users.
Ideally, I think we would
1) add new API
2) release new libnfnetlink and libnetfilter_* (where needed)
3) convert libnetfilter_* to use new API where reasonable
4) introduce API change to libnetfilter
5) adapt remaining handle_packet useres in libnetfilter* to changed api
6) release all of them together, incompatible with old versions.
Whcih is still messy. I would actually prefer if we'd not change existing API but rather only add new API's. Another alternative might be symbol versioning, though I've never used that before.
Cheers,
Harald
Signature · 5 lines
- Harald Welte <[email protected]> http://netfilter.org/ ============================================================================ "Fragmentation is like classful addressing -- an interesting early architectural error that shows how much experimentation was going on while IP was being designed." -- Paul Vixie
Quoted 17 lines · Harald Welte
Quoted 3 lines · Pablo Neira Ayuso
This patch introduces the following changes:
a)
nfnl_handle_msg: this function completes the message iterator API.looks nice to me.
Quoted 5 lines
b)
nfnl_handle_packet: This function is simpler interface to handle a netfilter netlink message. It loops over every message contained in a packet but, in this case, the programmer has no control on the looping process. Moreover, this function now has a done flag that is set under the same circunstances exposed above.this change looks also fine to me, but since it changes an existing function, it introduces library incompatibility between the users (libnetfilter_*) and libnfnetlink.
...
Quoted 10 lines
So how do we proceed?
I think at the moment, a new release of [most of] the libraries is needed due to accumulated bugfixes anyway. So I'd rather make a maintainance release with what we've got now than to introduce API changes. Addidional API (
nfnl_communicate,nfnl_handle_msg) is not a problem at all.As for the only API change (
nfnl_handle_packet), I would like to know if there is an urgent need for the 'done' flag in any of the users.
AFAIR, done is not required unless we are trying to copy someone else api type.
3 types of return values were permitted, <0, 0 and >0, by the function which now has "done" added. 0 meant continue, either <0 or >0 meant "stop now" and the other meant "stop after all messages in the currently read packet", it's hard to see how this doesn't provide what done provided; even with 2 values.
Although I submitted that patch that provided the return behaviour, I'm not fighting a case, just pointing out that I think this is adequate for the time beng.
Sam
Quoted 20 lines · Harald Welte
So how do we proceed?
I think at the moment, a new release of [most of] the libraries is needed due to accumulated bugfixes anyway. So I'd rather make a maintainance release with what we've got now than to introduce API changes. Addidional API (
nfnl_communicate,nfnl_handle_msg) is not a problem at all.As for the only API change (
nfnl_handle_packet), I would like to know if there is an urgent need for the 'done' flag in any of the users.Ideally, I think we would
1) add new API
2) release new libnfnetlink and libnetfilter_* (where needed)
3) convert libnetfilter_* to use new API where reasonable
4) introduce API change to libnetfilter
5) adapt remaininghandle_packetuseres in libnetfilter* to changed api
6) release all of them together, incompatible with old versions.
Quoted 3 lines
Whcih is still messy. I would actually prefer if we'd not change existing API but rather only add new API's. Another alternative might be symbol versioning, though I've never used that before.
I think that we can:
1) do the maintenance release without the new libnfnetlink API.
2) commit the patch attached that:
a) introduces nfnl_process_packet, that is similar to nfnl_handle_packet but it adds the done flag.
b) deprecates nfnl_handle_packet, marks this function as deprecated but keep it there to ensure backward compatibility. Maybe a message via stderr could tell the user that it must update, but I think that it is too much.
nfnl_listen and nfnl_talk should also go deprecated as soon as we move the existing libraries to the new API.
Signature · 1 line
Pablo
This patch introduces the following changes:
a) nfnl_handle_msg: this function completes the message iterator API.
nlh = nfnl_get_first_msg(h, ...);
while (nlh) {
int done;
...
ret = nfnl_handle_msg(h, &done);
if (ret < 0 || done)
return ret;
nlh = nfnl_get_next_msg(h, ...);
}Like this, we can iterate over the netlink messages that compose a packet. The message is processed by nfnl_handle_msg that calls the handler that was registered via nfnl_callback_register.
The done flag is set to one if the message is:
- an ACK/ERROR message
- a DONE message that notifies the end of a MULTI message.
b) nfnl_process_packet: This function is simpler interface to handle a netfilter netlink message. It loops over every message contained in a packet but, in this case, the programmer has no control on the looping process. Moreover, this function now has a done flag that is set under the same circunstances exposed above.
c) nfnl_communicate: This function supersedes nfnl_listen and nfnl_talk. It provides an interface to communicate with the nfnetlink subsystem.
- If the netlink header passed is null and a handler is registered via nfnl_callback_register, then it behaves like nfnl_listen.
- If the netlink header passed is non-null and no handler was registered via nfnl_callback_register, then it behaves like nfnl_talk.
d) it deprecates nfnl_handle_packet: nfnl_process_packet supersedes it.
src/libnfnetlink.c +70 -4
@@ -969,17 +969,28 @@ static int __nfnl_handle_msg(struct nfnlreturn 0 ; } -int nfnl_handle_packet (struct nfnl_handle *h,char *buf,int len) +int nfnl_process_packet (struct nfnl_handle *h,char *buf,int len,int *done) { +struct nlmsghdr *nlh = (struct nlmsghdr *)buf; -while (len >=NLMSG_SPACE (0 )) { +while (NLMSG_OK (nlh, len)) {u_int32_t rlen; -struct nlmsghdr *nlh = (struct nlmsghdr *)buf;if (nlh->nlmsg_len <sizeof (struct nlmsghdr ) || len < nlh->nlmsg_len)return -1 ; +/* This message is an ACK or a DONE */ +if (done && + (nlh->nlmsg_type ==NLMSG_ERROR || + (nlh->nlmsg_type ==NLMSG_DONE && + nlh->nlmsg_flags &NLM_F_MULTI ))) { +int err; + *done =1 ; +memcpy (&err,NLMSG_DATA (nlh),sizeof (int )); +return err; + } + rlen =NLMSG_ALIGN (nlh->nlmsg_len);if (rlen > len) rlen = len;
@@ -987,7 +998,62 @@ int nfnl_handle_packet(struct nfnl_handlif (__nfnl_handle_msg (h, nlh, rlen) <0 )return -1 ; - len -= rlen; + nlh =NLMSG_NEXT (nlh, len); }return 0 ; } + +int nfnl_handle_msg (struct nfnl_handle *h,int *done) +{ +int err =0 ; + +if (h->last_nlhdr->nlmsg_len >=NLMSG_SPACE (0 )) { +int len =NLMSG_ALIGN (h->last_nlhdr->nlmsg_len); + +if (h->last_nlhdr->nlmsg_len <sizeof (struct nlmsghdr ) + || len < h->last_nlhdr->nlmsg_len) +return -1 ; + +/* This message is an ACK or a DONE */ +if (done && (h->last_nlhdr->nlmsg_type ==NLMSG_ERROR || + (h->last_nlhdr->nlmsg_type ==NLMSG_DONE && + h->last_nlhdr->nlmsg_flags &NLM_F_MULTI ))) { + *done =1 ; +memcpy (&err,NLMSG_DATA (h->last_nlhdr),sizeof (int )); +return err; + } + + err =__nfnl_handle_msg (h, h->last_nlhdr, len); + } +return err; +} + +int nfnl_communicate (struct nfnl_handle *h,struct nlmsghdr *nlh) +{ +int ret, numbytes, done =0 ; +char buf[NFNL_BUFFSIZE ]; + +if (nlh) { + ret =nfnl_send (h, nlh); +if (ret <0 ) +return ret; + } + +while (1 ) { + numbytes =nfnl_recv (h, buf,sizeof (buf)); +if (numbytes <=0 ) +return numbytes; + + ret =nfnl_process_packet (h, buf, numbytes, &done); +if (ret <0 || done) +return ret; + } +return ret; +} + +/* Deprecated API */ + +int __deprecated nfnl_handle_packet (struct nfnl_handle *h,char *buf,int len) +{ +return nfnl_process_packet (h, buf, len,NULL ); +}
include/libnfnetlink/libnfnetlink.h +14 -1
@@ -71,6 +71,7 @@ extern int nfnl_talk(struct nfnl_handle unsigned, struct nlmsghdr *, int (*)(struct sockaddr_nl *, struct nlmsghdr *, void *), void *); +extern int nfnl_communicate (struct nfnl_handle *h,struct nlmsghdr *nlh);/* simple challenge/response */ extern int nfnl_listen(struct nfnl_handle *,
@@ -82,7 +83,8 @@ extern ssize_t nfnl_recv(const struct nfextern int nfnl_callback_register (struct nfnl_subsys_handle *,u_int8_t type,struct nfnl_callback *cb);extern int nfnl_callback_unregister (struct nfnl_subsys_handle *,u_int8_t type); -extern int nfnl_handle_packet (struct nfnl_handle *,char *buf,int len); +extern int nfnl_process_packet (struct nfnl_handle *,char *buf,int len,int *); +extern int nfnl_handle_msg (struct nfnl_handle *h,int *done);/* parsing */ extern struct nfattr *nfnl_parse_hdr(const struct nfnl_handle *nfnlh,
@@ -164,4 +166,15 @@ extern void nfnl_dump_packet(struct nlms# endif #endif +/* Deprecated API, keep it to ensure backward compatibility */ + +#if __GNUC_MINOR__ >0 +# ifndef __deprecated +# define __deprecated __attribute__((deprecated)) +# endif +#endif + +extern int __deprecated nfnl_handle_packet (struct nfnl_handle *,char *buf, +int len); +#endif /* __LIBNFNETLINK_H */
Quoted 8 lines · Amin Azez
AFAIR, done is not required unless we are trying to copy someone else api type.
3 types of return values were permitted, <0, 0 and >0, by the function which now has "done" added. 0 meant continue, either <0 or >0 meant "stop now" and the other meant "stop after all messages in the currently read packet", it's hard to see how this doesn't provide what done provided; even with 2 values.
Two kind of messages that mean "stop now" can make nfnl_handle_packet return 0.
a) ACK messages: When the client request some information with the NLM_F_ACK flag set.
b) DONE messages: At dumping, the last message received has the NLM_F_MULTI flag set (NLMSG_DONE) to notify that the dumping has finished.
Signature · 1 line
Pablo
Quoted 12 lines · Pablo Neira Ayuso
Quoted 8 lines · Amin Azez
AFAIR, done is not required unless we are trying to copy someone else api type.
3 types of return values were permitted, <0, 0 and >0, by the function which now has "done" added. 0 meant continue, either <0 or >0 meant "stop now" and the other meant "stop after all messages in the currently read packet", it's hard to see how this doesn't provide what done provided; even with 2 values.
Quoted 8 lines
Two kind of messages that mean "stop now" can make
nfnl_handle_packetreturn 0.a) ACK messages: When the client request some information with the
NLM_F_ACKflag set.
b) DONE messages: At dumping, the last message received has theNLM_F_MULTIflag set (NLMSG_DONE) to notify that the dumping has finished.
I was talking about values returned by the user callback handler that can stop the read loop before all messages are exhausted.
Sam