passt

History

David Gibson ba74b1fea1 doc: Extend zero-recv test with methods using msghdr This test program verifies that we can receive and discard datagrams by using recv() with a NULL buffer and zero-length. Extend it to verify it also works using recvmsg() and either an iov with a zero-length NULL buffer or an iov that itself is NULL and zero-length. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> [sbrivio: Fixed printf() message in main of recv-zero.c] Signed-off-by: Stefano Brivio <sbrivio@redhat.com>		2024-07-17 15:31:02 +02:00
..
.gitignore	doc: Test behaviour of closing duplicate UDP sockets	2024-07-17 15:30:14 +02:00
common.c	doc: Add program to document and test assumptions about SO_REUSEADDR	2024-07-05 15:26:43 +02:00
common.h	doc: Add program to document and test assumptions about SO_REUSEADDR	2024-07-05 15:26:43 +02:00
Makefile	doc: Test behaviour of closing duplicate UDP sockets	2024-07-17 15:30:14 +02:00
README	doc: Add program to document and test assumptions about SO_REUSEADDR	2024-07-05 15:26:43 +02:00
recv-zero.c	doc: Extend zero-recv test with methods using msghdr	2024-07-17 15:31:02 +02:00
reuseaddr-priority.c	doc: Trivial fix for reuseaddr-priority	2024-07-15 17:55:52 +02:00
udp-close-dup.c	doc: Test behaviour of closing duplicate UDP sockets	2024-07-17 15:30:14 +02:00

README

Platform Requirements
=====================

TODO: document the various Linux specific features we currently require


Test Programs
-------------

In some places we rely on quite specific behaviour of sockets.
Although Linux, at least, seems to behave as required, It's not always
clear from the available documentation if this is required by POSIX or
some other specification.

To specifically document those expectations this directory has some
test programs which explicitly check for the behaviour we need.
When/if we attempt a port to a new platform, running these to check
behaviour would be a good place to start.