syscalls/sendmmsg: add new test
PATCH v3 1/1 syscalls/sendmmsg: add new test
Test basic functionality of sendmmsg and recvmmsg.
---
Changes since v2:
- fix race between sender and receiver
- use TST_GET_UNUSED_PORT
- fix checkpatch error (it still complains about the // on the SPDX identifier in sendmmsg_var.h, but other headers in this project use that style)
- add SPDX identifier in sendmmsg01.c
Changes since v1:
- rebased on recent autotools cleanup for libc func checks
- used test_variant to test direct syscalls and libc syscalls
- use tst_syscall instead of ltp_syscall
- check that both messages have been sent, retry sending messages if necessary
- use tst_brk(TBROK... if sendmmsg fails so recv thread is not kept waiting
configure.ac | 3 + include/lapi/socket.h | 8 + runtest/syscalls | 2 + testcases/kernel/syscalls/sendmmsg/.gitignore | 1 + testcases/kernel/syscalls/sendmmsg/Makefile | 9 + .../kernel/syscalls/sendmmsg/sendmmsg01.c | 162 ++++++++++++++++++ .../kernel/syscalls/sendmmsg/sendmmsg_var.h | 60 +++++++ 7 files changed, 245 insertions(+) create mode 100644 testcases/kernel/syscalls/sendmmsg/.gitignore create mode 100644 testcases/kernel/syscalls/sendmmsg/Makefile create mode 100644 testcases/kernel/syscalls/sendmmsg/sendmmsg01.c create mode 100644 testcases/kernel/syscalls/sendmmsg/sendmmsg_var.h
configure.ac +3 -0
@@ -82,9 +82,11 @@ AC_CHECK_FUNCS([ \ pwritev \ pwritev2 \ readlinkat \ + recvmmsg \ renameat \ renameat2 \ sched_getcpu \ + sendmmsg \ sigpending \ splice \ stime \
@@ -253,6 +255,7 @@ LTP_CHECK_TIME LTP_CHECK_TIMERFD test "x$with_tirpc" = xyes && LTP_CHECK_TIRPC LTP_CHECK_TPACKET_V3 +LTP_CHECK_MMSGHDR LTP_CHECK_UNAME_DOMAINNAME LTP_CHECK_XFS_QUOTACTL LTP_CHECK_X_TABLES
include/lapi/socket.h +8 -0
@@ -19,6 +19,7 @@#ifndef __LAPI_SOCKET_H__#define __LAPI_SOCKET_H__ +#include "config.h" #include <sys/socket.h> #ifndef MSG_ZEROCOPY
@@ -69,4 +70,11 @@# define SOL_ALG 279#endif +#ifndef HAVE_STRUCT_MMSGHDR +struct mmsghdr { +struct msghdr msg_hdr; +unsigned int msg_len; +}; +#endif +#endif /* __LAPI_SOCKET_H__ */
runtest/syscalls +2 -0
@@ -1117,6 +1117,8 @@ sendfile09_64 sendfile09_64 sendmsg01 sendmsg01 sendmsg02 sendmsg02 +sendmmsg01 sendmmsg01 + sendto01 sendto01 sendto02 sendto02
testcases/kernel/syscalls/sendmmsg/.gitignore new file +1 -0
@@ -0,0 +1 @@ +sendmmsg01
testcases/kernel/syscalls/sendmmsg/Makefile new file +9 -0
@@ -0,0 +1,9 @@ +# SPDX-License-Identifier: GPL-2.0-or-later + +top_srcdir ?= ../../../.. + +sendmmsg01: CFLAGS+=-pthread + +include $(top_srcdir)/include/mk/testcases.mk + +include $(top_srcdir)/include/mk/generic_leaf_target.mk
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +162 -0
162 lines not on this page · raw message
testcases/kernel/syscalls/sendmmsg/sendmmsg_var.h new file +60 -0
60 lines not on this page · raw message
Signature · 1 line
2.22.0.657.g960e92d24f-goog
PATCH v3 1/1 syscalls/sendmmsg: add new test
Hi!
Quoted 52 lines
Test basic functionality of sendmmsg and recvmmsg.
Signed-off-by Steve Muckle <[email protected]>---
Changes since v2:
- fix race between sender and receiver
- useTST_GET_UNUSED_PORT
- fix checkpatch error (it still complains about the // on the SPDX identifier insendmmsg_var.h, but other headers in this project use that style)
- add SPDX identifier insendmmsg01.cChanges since v1:
- rebased on recent autotools cleanup for libc func checks
- usedtest_variantto test direct syscalls and libc syscalls
- usetst_syscallinstead ofltp_syscall
- check that both messages have been sent, retry sending messages if necessary
- use tst_brk(TBROK... if sendmmsg fails so recv thread is not kept waitingconfigure.ac | 3 + include/lapi/socket.h | 8 + runtest/syscalls | 2 + testcases/kernel/syscalls/sendmmsg/.gitignore | 1 + testcases/kernel/syscalls/sendmmsg/Makefile | 9 + .../kernel/syscalls/sendmmsg/sendmmsg01.c | 162 ++++++++++++++++++ .../kernel/syscalls/sendmmsg/sendmmsg_var.h | 60 +++++++ 7 files changed, 245 insertions(+) create mode 100644 testcases/kernel/syscalls/sendmmsg/.gitignore create mode 100644 testcases/kernel/syscalls/sendmmsg/Makefile create mode 100644 testcases/kernel/syscalls/sendmmsg/sendmmsg01.c create mode 100644 testcases/kernel/syscalls/sendmmsg/sendmmsg_var.hconfigure.ac +2
-0@@ -82,9 +82,11 @@ AC_CHECK_FUNCS([ \ pwritev \ pwritev2 \ readlinkat \ + recvmmsg \ renameat \ renameat2 \ sched_getcpu \ + sendmmsg \ sigpending \ splice \ stime \
configure.ac LTP_CHECK_TIME · line 258
Quoted 4 lines
configure.ac +1
-0@@ -253,6 +255,7 @@ LTP_CHECK_TIME LTP_CHECK_TIMERFD test "x$with_tirpc" = xyes && LTP_CHECK_TIRPC LTP_CHECK_TPACKET_V3 +LTP_CHECK_MMSGHDR
This seems to be already there under the # custom functions comment.
Also there is mmsghdr definition in the cve-2016-7117.c we should include the lapi/socket.h there later on...
Quoted 99 lines
configure.ac +0
-0LTP_CHECK_UNAME_DOMAINNAME LTP_CHECK_XFS_QUOTACTL LTP_CHECK_X_TABLESinclude/lapi/socket.h +8
-0@@ -19,6 +19,7 @@#ifndef __LAPI_SOCKET_H__#define __LAPI_SOCKET_H__ +#include "config.h" #include <sys/socket.h> #ifndef MSG_ZEROCOPY @@ -69,4 +70,11 @@# define SOL_ALG 279#endif +#ifndef HAVE_STRUCT_MMSGHDR +struct mmsghdr { +struct msghdr msg_hdr; +unsigned int msg_len; +}; +#endif +#endif /* __LAPI_SOCKET_H__ */ runtest/syscalls +2
-0@@ -1117,6 +1117,8 @@ sendfile09_64 sendfile09_64 sendmsg01 sendmsg01 sendmsg02 sendmsg02 +sendmmsg01 sendmmsg01 + sendto01 sendto01 sendto02 sendto02testcases/kernel/syscalls/sendmmsg/.gitignore new file +1
-0@@ -0,0 +1 @@ +sendmmsg01testcases/kernel/syscalls/sendmmsg/Makefile new file +9
-0@@ -0,0 +1,9 @@ +# SPDX-License-Identifier: GPL-2.0-or-later + +top_srcdir ?= ../../../.. + +sendmmsg01: CFLAGS+=-pthread + +include $(top_srcdir)/include/mk/testcases.mk + +include $(top_srcdir)/include/mk/generic_leaf_target.mktestcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +31
-0@@ -0,0 +1,162 @@ +// SPDX-License-Identifier: GPL-2.0-or-later +/* +* This test is based on source contained in the man pages for sendmmsg and +* recvmmsg in release 4.15 of the Linux man-pages project. +*/ + +#define _GNU_SOURCE +#include <netinet/ip.h> +#include <semaphore.h> +#include <stdio.h> +#include <stdlib.h> +#include <string.h> +#include <sys/types.h> + +#include "tst_test.h" +#include "lapi/socket.h" +#include "tst_safe_macros.h" +#include "tst_safe_pthread.h" + +#include "sendmmsg_var.h" + +#define BUFSIZE 16 +#define VLEN 2 + +static sem_t send_sem; +static unsigned int port; + +static void *sender_thread(LTP_ATTRIBUTE_UNUSED void *arg) +{ +struct sockaddr_in addr; +struct mmsghdr msg[VLEN ];
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c line 41
Quoted 10 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +10
-0+struct iovec msg1[2 ], msg2; +int send_sockfd; +int msgs =VLEN ; +int retval; + + send_sockfd =SAFE_SOCKET (AF_INET ,SOCK_DGRAM ,0 ); + + addr.sin_family =AF_INET ; + addr.sin_addr.s_addr =htonl (INADDR_LOOPBACK ); + addr.sin_port =htons (port);
The port returned by TST_GET_UNUSED_PORT() is already in network byte order, we found a bug recently where test was failing randomly since if we attempt to convert the value we may end up with priviledged port number if we are unlucky.
Quoted 23 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +23
-0+SAFE_CONNECT (send_sockfd, (struct sockaddr *) &addr,sizeof (addr)); + +memset (msg1,0 ,sizeof (msg1)); + msg1[0 ].iov_base ="one" ; + msg1[0 ].iov_len =3 ; + msg1[1 ].iov_base ="two" ; + msg1[1 ].iov_len =3 ; + +memset (&msg2,0 ,sizeof (msg2)); + msg2.iov_base ="three" ; + msg2.iov_len =5 ; + +memset (msg,0 ,sizeof (msg)); + msg[0 ].msg_hdr.msg_iov = msg1; + msg[0 ].msg_hdr.msg_iovlen =2 ; + + msg[1 ].msg_hdr.msg_iov = &msg2; + msg[1 ].msg_hdr.msg_iovlen =1 ; + +sem_wait (&send_sem); + +while (msgs) { + retval =do_sendmmsg (send_sockfd, msg, msgs,0 );
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c line 74
Quoted 10 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +10
-0+if (retval <0 ) { +/* +* tst_brk is used here so reader is not left waiting +* for data - note timeout for recvmmsg does not work +* as one would expect (see man page) +*/ +tst_brk (TBROK |TTERRNO ,"sendmmsg failed" ); + goto out; + } + msgs -= retval;
Wouldn't this resend the start of the message again if we got interrupted in the middle?
I guess that the correct retry would loop over the messages and decrement the iov_len and shift the buffers based on the msg_len. Something as:
retry:
retval = do_sendmmsg(send_sockfd, msg, msgs, 0);
for (i = 0; i < retval; i++) {
int transmitted = msg[i].msg_len;
msg[i].msg_len = 0;
for (j = 0; j < msg[i].msg_iovlen; j++) {
int len = msg[i].msg_iov[j].msg_iovlen;
/* whole buffer send */
if (transmitted >= len) {
transmitted -= len;
msg[i].msg_iov[j].msg_iovlen = 0;
continue;
}
msg[i].msg_iov[j].msg_iovlen -= transmitted;
msg[i].msg_iov[j].msg_iov += transmitted;
goto retry;
}
}Also I'm pretty sure that we will actually happen to write the whole buffer unless we fill up the kernel buffers, which we hardly will with a few bytes. So maybe we should just send the message here and check that the msg_len are filled correctly in this case.
Quoted 12 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +12
-0+ } + +out: +SAFE_CLOSE (send_sockfd); +return NULL ; +} + + +static void *receiver_thread(LTP_ATTRIBUTE_UNUSED void *arg) +{ +int receive_sockfd; +struct sockaddr_in addr;
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c line 96
Quoted 10 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +10
-0+struct mmsghdr msgs[VLEN ]; +struct iovec iovecs[VLEN ]; +char bufs[VLEN ][BUFSIZE +1 ]; +struct timespec timeout; +int i, retval; + + receive_sockfd =SAFE_SOCKET (AF_INET ,SOCK_DGRAM ,0 ); + addr.sin_family =AF_INET ; + addr.sin_addr.s_addr =htonl (INADDR_LOOPBACK ); + addr.sin_port =htons (port);
Here as well, the htons() should be dropped.
Quoted 138 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +66
-0+SAFE_BIND (receive_sockfd, (struct sockaddr *)&addr,sizeof (addr)); + +sem_post (&send_sem); + +memset (msgs,0 ,sizeof (msgs)); +for (i =0 ; i <VLEN ; i++) { + iovecs[i].iov_base = bufs[i]; + iovecs[i].iov_len =BUFSIZE ; + msgs[i].msg_hdr.msg_iov = &iovecs[i]; + msgs[i].msg_hdr.msg_iovlen =1 ; + } + + timeout.tv_sec =1 ; + timeout.tv_nsec =0 ; + + retval =do_recvmmsg (receive_sockfd, msgs,VLEN ,0 , &timeout); +SAFE_CLOSE (receive_sockfd); + +if (retval ==-1 ) { +tst_res (TFAIL |TTERRNO ,"recvmmsg failed" ); +return NULL ; + } +if (retval !=2 ) { +tst_res (TFAIL ,"Received unexpected number of messages (%d)" , + retval); +return NULL ; + } + + bufs[0 ][msgs[0 ].msg_len] =0 ; +if (strcmp (bufs[0 ],"onetwo" )) +tst_res (TFAIL ,"Error in first received message." ); +else +tst_res (TPASS ,"First message received successfully." ); + + bufs[1 ][msgs[1 ].msg_len] =0 ; +if (strcmp (bufs[1 ],"three" )) +tst_res (TFAIL ,"Error in second received message." ); +else +tst_res (TPASS ,"Second message received successfully." ); + +return NULL ; +} + +static void run (void ) +{ +pthread_t sender; +pthread_t receiver; + +SAFE_PTHREAD_CREATE (&sender,NULL , sender_thread,NULL ); +SAFE_PTHREAD_CREATE (&receiver,NULL , receiver_thread,NULL ); +SAFE_PTHREAD_JOIN (sender,NULL ); +SAFE_PTHREAD_JOIN (receiver,NULL ); +} + +static void setup (void ) +{ +sem_init (&send_sem,0 ,0 ); + port =TST_GET_UNUSED_PORT (AF_INET ,SOCK_DGRAM ); +test_info (); +} + +static struct tst_test test = { + .test_all = run, + .setup = setup, + .test_variants =TEST_VARIANTS , +};testcases/kernel/syscalls/sendmmsg/sendmmsg_var.h new file +60
-0@@ -0,0 +1,60 @@ +// SPDX-License-Identifier: GPL-2.0-or-later +/* +* Copyright (c) 2018 Google, Inc. +*/ + +#ifndef SENDMMSG_VAR__ +#define SENDMMSG_VAR__ + +#include "lapi/syscalls.h" + +static int do_sendmmsg (int sockfd,struct mmsghdr *msgvec,unsigned int vlen, +int flags) +{ +switch (tst_variant) { +case 0 : +return tst_syscall (__NR_sendmmsg, sockfd, msgvec, vlen, flags); +case 1 : +#ifdef HAVE_SENDMMSG +return sendmmsg (sockfd, msgvec, vlen, flags); +#else +tst_brk (TCONF ,"libc sendmmsg not present" ); +#endif + } + +return -1 ; +} + +static int do_recvmmsg (int sockfd,struct mmsghdr *msgvec,unsigned int vlen, +int flags,struct timespec *timeout) +{ +switch (tst_variant) { +case 0 : +return tst_syscall (__NR_recvmmsg, sockfd, msgvec, vlen, flags, + timeout); +case 1 : +#ifdef HAVE_RECVMMSG +return recvmmsg (sockfd, msgvec, vlen, flags, timeout); +#else +tst_brk (TCONF ,"libc recvmmsg not present" ); +#endif + } + +return -1 ; +} + +static void test_info (void ) +{ +switch (tst_variant) { +case 0 : +tst_res (TINFO ,"Testing direct sendmmsg and recvmmsg syscalls" ); +break ; +case 1 : +tst_res (TINFO ,"Testing libc sendmmsg and recvmmsg syscalls" ); +break ; + } +} + +#define TEST_VARIANTS 2 + +#endif /* SENDMMSG_VAR__ */ Signature · 5 lines
2.22.0.657.g960e92d24f-goog -- Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 2 lines
Cyril Hrubis [email protected]
PATCH v3 1/1 syscalls/sendmmsg: add new test
Hi Cyril, thanks for your feedback.
Quoted 15 lines · Cyril Hrubis
Quoted 15 lines
configure.ac +2
-0@@ -82,9 +82,11 @@ AC_CHECK_FUNCS([ \ pwritev \ pwritev2 \ readlinkat \ + recvmmsg \ renameat \ renameat2 \ sched_getcpu \ + sendmmsg \ sigpending \ splice \
Quoted 8 lines
configure.ac LTP_CHECK_TIME · line 258
Quoted 6 lines
configure.ac +1
-0stime \@@ -253,6 +255,7 @@ LTP_CHECK_TIME LTP_CHECK_TIMERFD test "x$with_tirpc" = xyes && LTP_CHECK_TIRPC LTP_CHECK_TPACKET_V3 +LTP_CHECK_MMSGHDRThis seems to be already there under the # custom functions comment.
Ah yes looks like this got added while I was sitting on the patch, and I failed to notice it when I rebased. Removed.
Quoted 8 lines
configure.ac LTP_CHECK_TIME · line 261
Quoted 3 lines
configure.ac +3
-0+ addr.sin_family = AF_INET; + addr.sin_addr.s_addr = htonl(INADDR_LOOPBACK); + addr.sin_port = htons(port);The port returned by
TST_GET_UNUSED_PORT()is already in network byte order, we found a bug recently where test was failing randomly since if we attempt to convert the value we may end up with priviledged port number if we are unlucky.
Fixed.
Quoted 29 lines
Quoted 29 lines
configure.ac +28
-0+ SAFE_CONNECT(send_sockfd, (struct sockaddr *) &addr, sizeof(addr)); + + memset(msg1, 0, sizeof(msg1)); + msg1[0].iov_base = "one"; + msg1[0].iov_len = 3; + msg1[1].iov_base = "two"; + msg1[1].iov_len = 3; + + memset(&msg2, 0, sizeof(msg2)); + msg2.iov_base = "three"; + msg2.iov_len = 5; + + memset(msg, 0, sizeof(msg)); + msg[0].msg_hdr.msg_iov = msg1; + msg[0].msg_hdr.msg_iovlen = 2; + + msg[1].msg_hdr.msg_iov = &msg2; + msg[1].msg_hdr.msg_iovlen = 1; + + sem_wait(&send_sem); + + while (msgs) { + retval = do_sendmmsg(send_sockfd, msg, msgs, 0); + if (retval < 0) { + /* + * tst_brk is used here so reader is not left waiting + * for data - note timeout for recvmmsg does not work + * as one would expect (see man page)
Quoted 8 lines
configure.ac
Quoted 5 lines
configure.ac +5
-0+ */ + tst_brk(TBROK|TTERRNO, "sendmmsg failed"); + goto out; + } + msgs -= retval;Wouldn't this resend the start of the message again if we got interrupted in the middle?
The failure modes aren't clear to me. Based on the man page for sendmmsg it sounded like it returns the number of messages successfully sent, and I assumed that unsuccessfully sent messages were not partially sent? The sendmsg page says that it only sends messages that can fit atomically in the underlying protocol.
Quoted 27 lines
I guess that the correct retry would loop over the messages and decrement the
iov_lenand shift the buffers based on themsg_len. Something as:retry:
retval = do_sendmmsg(send_sockfd, msg, msgs, 0); for (i = 0; i < retval; i++) { int transmitted = msg[i].msg_len; msg[i].msg_len = 0; for (j = 0; j < msg[i].msg_iovlen; j++) { int len = msg[i].msg_iov[j].msg_iovlen; /* whole buffer send */ if (transmitted >= len) { transmitted -= len; msg[i].msg_iov[j].msg_iovlen = 0; continue; } msg[i].msg_iov[j].msg_iovlen -= transmitted; msg[i].msg_iov[j].msg_iov += transmitted; goto retry; } }
Quoted 4 lines
Also I'm pretty sure that we will actually happen to write the whole buffer unless we fill up the kernel buffers, which we hardly will with a few bytes. So maybe we should just send the message here and check that the
msg_lenare filled correctly in this case.
That works for me, after all if we get unlucky and cannot send the first message in the vector, sendmmsg() returns an error and the test will fail. So retrying on the second message is a bit inconsistent.
Quoted 3 lines
configure.ac
Quoted 1 line
configure.ac +1
-0+ addr.sin_port = htons(port);Here as well, the
htons()should be dropped.
Fixed.
thanks,
steve
PATCH v3 1/1 syscalls/sendmmsg: add new test
Hi!
Quoted 16 lines
Quoted 7 lines
Quoted 7 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +7
-0+while (msgs) { + retval =do_sendmmsg (send_sockfd, msg, msgs,0 ); +if (retval <0 ) { +/* +* tst_brk is used here so reader is not left waiting +* for data - note timeout for recvmmsg does not work +* as one would expect (see man page) Quoted 8 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c line 74
Quoted 5 lines
testcases/kernel/syscalls/sendmmsg/sendmmsg01.c new file +5
-0+*/ +tst_brk (TBROK |TTERRNO ,"sendmmsg failed" ); + goto out; + } + msgs -= retval;Wouldn't this resend the start of the message again if we got interrupted in the middle?
Quoted 5 lines
The failure modes aren't clear to me. Based on the man page for sendmmsg it sounded like it returns the number of messages successfully sent, and I assumed that unsuccessfully sent messages were not partially sent? The sendmsg page says that it only sends messages that can fit atomically in the underlying protocol.
Looking at the kernel code for sendmmsg() it's just a simple loop that calls sendmsg() for each msghdr in the struct mmsghdr with a special MSG_BATCH flag for all but the last message, see net/socket.c and as far as I can tell it just loops over the msgvec so each individual message should behave like it was send with sendmsg() and the return value from sendmsg() is stored in the msg_len field. The return value from sendmmsg() describes the number of updated elements of the struct mmsghdr vector, not necessarily all the data from the last updated msg_hdr are send.
Now it depends on if the file descriptor is blocking or non-blocking and also on the particular protocol.
Generally blocking call should return either with error or with all data send, which is also default. However for some protocols we may as well get first positive number i.e. part of the buffer send, then next call would return an error.
If it's non-blocking (we did fcntl() with O_NONBLOCK or passed MSG_DONTWAIT) we may return early with partial buffer send/received if the operation would block i.e. socket send buffer full/no data ready.
For the case of UDP looking at the udp_sendmsg() as far as I can tell it either returns error or sends everything either way and this makese sense because we even do not care if there is anyone listening on the other side and we are allowed to drop the datagram anyways. I guess that for TCP we may write part of buffers for quite a lot of different reasons.
Also for UDP as far as I can tell the maximal atomic message size is 0xFFFF. Which would be limit of the 16 bit field lengh in UDP header, at least that is what is checked for at the start of the udp_sendmsg() which we end up calling for the socket here.
To sum it up, in our very simple case we do not care about retrying at all.
Quoted 27 lines
Quoted 27 lines
I guess that the correct retry would loop over the messages and decrement the
iov_lenand shift the buffers based on themsg_len. Something as:retry:
retval = do_sendmmsg(send_sockfd, msg, msgs, 0); for (i = 0; i < retval; i++) { int transmitted = msg[i].msg_len; msg[i].msg_len = 0; for (j = 0; j < msg[i].msg_iovlen; j++) { int len = msg[i].msg_iov[j].msg_iovlen; /* whole buffer send */ if (transmitted >= len) { transmitted -= len; msg[i].msg_iov[j].msg_iovlen = 0; continue; } msg[i].msg_iov[j].msg_iovlen -= transmitted; msg[i].msg_iov[j].msg_iov += transmitted; goto retry; } }
Quoted 8 lines
Quoted 4 lines
Also I'm pretty sure that we will actually happen to write the whole buffer unless we fill up the kernel buffers, which we hardly will with a few bytes. So maybe we should just send the message here and check that the
msg_lenare filled correctly in this case.That works for me, after all if we get unlucky and cannot send the first message in the vector,
sendmmsg()returns an error and the test will fail. So retrying on the second message is a bit inconsistent.
Agreed all we should care about is that the return value from sendmmsg() is correct and that the msg_len fields are updated correctly.
Signature · 2 lines
Cyril Hrubis [email protected]