mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Ossama Othman <ossama.othman@gmail.com>
To: mptcp@lists.linux.dev
Subject: mptcpd 0.10 released
Date: Fri, 24 Jun 2022 13:58:44 -0700	[thread overview]
Message-ID: <CAE+88WNQ4J5iBNZMOnLkh+iUgXSQOaHL5ZcU30T4fC0ovh9zrA@mail.gmail.com> (raw)

Mptcpd 0.10 is now available at:

    https://github.com/intel/mptcpd/releases/tag/v0.10

Notable changes include the following:

- Inconsistent byte order handling in mptcpd was corrected.  IP ports
  sent in path management commands and events now have the correct
  byte order.  Furthermore, the mptcpd unit test suite no longer
  assumes that the tests will be run on a little endian host.  IPv4
  addresses and IP ports used in the mptcpd unit test suite are now
  byte swapped as needed according to the endianness of the platform.
  As always, IPv4 addresses and IP ports passed through pointers to
  struct sockaddr should be in network byte order by convention.

- A potential memory violation caused when attempting to register NULL
  networking monitoring operations with mptcpd was fixed.

- Mptcpd now supports gcc 12.  Link-time errors found in gcc 12 mptcpd
  builds were fixed.

- ELL 0.45 or greater is supported.

- Code coverage was further expanded.

- The mptcpd network monitor supports loopback interface monitoring if
  so desired.

- Improved support for reproducible builds by disabling HTML
  timestamps in Doxygen generated mptcpd documentation.

- Some mptcpd unit tests will be skipped rather than allowed to fail
  on hosts running a kernel without MPTCP support.

                 reply	other threads:[~2022-06-24 20:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAE+88WNQ4J5iBNZMOnLkh+iUgXSQOaHL5ZcU30T4fC0ovh9zrA@mail.gmail.com \
    --to=ossama.othman@gmail.com \
    --cc=mptcp@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).