XREQ and others race on TTL.

The TTL in these cases should have been atomic.  To facilitate
things we actually introduce an atomic int for convenience.  We
also introduce a convenience nni_msg_must_append_u32() and
nni_msg_header_must_append_u32(), so that we can eliminate some
failure tests that cannot ever happen.  Combined with a new test
for xreq, we have 100% coverage for xreq and more coverage for
the other REQ/REP protocols.

1 files changed, 8 insertions, 0 deletions

diff --git a/src/platform/posix/posix_impl.h b/src/platform/posix/posix_impl.h
index a1cb62c5..3ec66b6b 100644
--- a/src/platform/posix/posix_impl.h
+++ b/src/platform/posix/posix_impl.h
@@ -83,6 +83,10 @@ struct nni_atomic_flag {
 	atomic_flag f;
 };
 
+struct nni_atomic_int {
+	atomic_int v;
+};
+
 struct nni_atomic_u64 {
 	atomic_uint_fast64_t v;
 };
@@ -100,6 +104,10 @@ struct nni_atomic_bol {
 	bool b;
 };
 
+struct nni_atomic_int {
+	int v;
+};
+
 struct nni_atomic_u64 {
 	uint64_t v;
 };