aboutgitcodebugslistschat
path: root/contrib
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2025-03-19 16:14:21 +1100
committerStefano Brivio <sbrivio@redhat.com>2025-03-19 15:25:12 +0100
commit28772ee91a60b34786023496ea17c2c2f4e5f7f5 (patch)
tree9c5b4721c217bf7c28508e47c09810a25b5e43ef /contrib
parent51f3c071a76bd20677e72b49007b822dca71e755 (diff)
downloadpasst-28772ee91a60b34786023496ea17c2c2f4e5f7f5.tar
passt-28772ee91a60b34786023496ea17c2c2f4e5f7f5.tar.gz
passt-28772ee91a60b34786023496ea17c2c2f4e5f7f5.tar.bz2
passt-28772ee91a60b34786023496ea17c2c2f4e5f7f5.tar.lz
passt-28772ee91a60b34786023496ea17c2c2f4e5f7f5.tar.xz
passt-28772ee91a60b34786023496ea17c2c2f4e5f7f5.tar.zst
passt-28772ee91a60b34786023496ea17c2c2f4e5f7f5.zip
migrate, tcp: More careful marshalling of mss parameter during migration
During migration we extract the limit on segment size using TCP_MAXSEG, and set it on the other side with TCP_REPAIR_OPTIONS. However, unlike most 32-bit values we transfer we transfer it in native endian, not network endian. This is not correct; add it to the list of endian fixups we make. In addition, while MAXSEG will be 32-bits in practice, and is given as such to TCP_REPAIR_OPTIONS, the TCP_MAXSEG sockopt treats it as an 'int'. It's not strictly safe to pass a uint32_t to a getsockopt() expecting an int, although we'll get away with it on most (maybe all) platforms. Correct this as well. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> [sbrivio: Minor coding style fix] Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions