From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v3 0/1] Improve validation of --mtu option
Date: Fri, 21 Feb 2025 13:35:02 +1100 [thread overview]
Message-ID: <20250221023503.2170668-1-david@gibson.dropbear.id.au> (raw)
Here are some of the more straightforward parts of my patches making
various MTU related fixes. These ones improve how we validate the
--mtu option.
Changes since v2:
* Don't disable a protocol because the MTU is too small, just warn.
It's only an advertised MTU, not an enforced MTU
David Gibson (1):
conf: Be more precise about minimum MTUs
conf.c | 18 +++++++++++++++---
ip.h | 7 +++++++
util.h | 6 ------
3 files changed, 22 insertions(+), 9 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-21 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 2:35 David Gibson [this message]
2025-02-21 2:35 ` [PATCH v3 1/1] conf: Be more precise about minimum MTUs David Gibson
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=20250221023503.2170668-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).