Joan Lledó, le ven. 03 mai 2019 13:34:33 +0200, a ecrit:
> Missatge de Samuel Thibault del dia dj., 2
> de maig 2019 a les 23:55:
> > Put another way: instead, we have to go through flags which we see
> > happen in the wild, and take appropriate measures (which may really be
> > to just let lwip_s
Missatge de Samuel Thibault del dia dj., 2
de maig 2019 a les 23:55:
> Put another way: instead, we have to go through flags which we see
> happen in the wild, and take appropriate measures (which may really be
> to just let lwip_sendmsg return EINVAL, or do the check ourselves if
> lwip_sendmsg d
Samuel Thibault, le jeu. 02 mai 2019 23:53:41 +0200, a ecrit:
> Joan Lledó, le jeu. 02 mai 2019 11:54:59 +0200, a ecrit:
> > Lwip 2.1.2 added a new assertion to ensure that no unsupported flags
> > are being sent to lwip_sendmsg(). The send operation must be updated to
> > remove this u
Joan Lledó, le jeu. 02 mai 2019 11:54:59 +0200, a ecrit:
> Lwip 2.1.2 added a new assertion to ensure that no unsupported flags
> are being sent to lwip_sendmsg(). The send operation must be updated to
> remove this unsupported flags.
> @@ -361,8 +361,11 @@ struct msghdr m = { msg_name
Lwip 2.1.2 added a new assertion to ensure that no unsupported flags
are being sent to lwip_sendmsg(). The send operation must be updated to
remove this unsupported flags.
* lwip/socket-ops.c: lwip_S_socket_send(): Remove unsupported flags.
---
lwip/socket-ops.c | 13 -
