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 v2 4/9] packet: Give explicit name to maximum packet size
Date: Wed, 12 Mar 2025 13:18:34 +1100 [thread overview]
Message-ID: <20250312021839.2405877-5-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20250312021839.2405877-1-david@gibson.dropbear.id.au>
We verify that every packet we store in a pool (and every partial packet
we retreive from it) has a length no longer than UINT16_MAX. This
originated in the older packet pool implementation which stored packet
lengths in a uint16_t. Now, that packets are represented by a struct
iovec with its size_t length, this check serves only as a sanity / security
check that we don't have some wildly out of range length due to a bug
elsewhere.
We have may reasons to (slightly) increase this limit in future, so in
preparation, give this quantity an explicit name - PACKET_MAX_LEN.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
packet.c | 4 ++--
packet.h | 3 +++
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/packet.c b/packet.c
index 0330b548..bcac0375 100644
--- a/packet.c
+++ b/packet.c
@@ -83,7 +83,7 @@ void packet_add_do(struct pool *p, size_t len, const char *start,
if (packet_check_range(p, start, len, func, line))
return;
- if (len > UINT16_MAX) {
+ if (len > PACKET_MAX_LEN) {
trace("add packet length %zu, %s:%i", len, func, line);
return;
}
@@ -119,7 +119,7 @@ void *packet_get_do(const struct pool *p, size_t idx, size_t offset,
return NULL;
}
- if (len > UINT16_MAX) {
+ if (len > PACKET_MAX_LEN) {
if (func) {
trace("packet data length %zu, %s:%i",
len, func, line);
diff --git a/packet.h b/packet.h
index bdc07fef..d099f026 100644
--- a/packet.h
+++ b/packet.h
@@ -6,6 +6,9 @@
#ifndef PACKET_H
#define PACKET_H
+/* Maximum size of a single packet stored in pool, including headers */
+#define PACKET_MAX_LEN UINT16_MAX
+
/**
* struct pool - Generic pool of packets stored in a buffer
* @buf: Buffer storing packet descriptors,
--
@@ -6,6 +6,9 @@
#ifndef PACKET_H
#define PACKET_H
+/* Maximum size of a single packet stored in pool, including headers */
+#define PACKET_MAX_LEN UINT16_MAX
+
/**
* struct pool - Generic pool of packets stored in a buffer
* @buf: Buffer storing packet descriptors,
--
2.48.1
next prev parent reply other threads:[~2025-03-12 3:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 2:18 [PATCH v2 0/9] Improve handling of MTU limits David Gibson
2025-03-12 2:18 ` [PATCH v2 1/9] conf: Use the same optstring for passt and pasta modes David Gibson
2025-03-12 2:18 ` [PATCH v2 2/9] conf: Move mode detection into helper function David Gibson
2025-03-12 2:18 ` [PATCH v2 3/9] conf: Detect vhost-user mode earlier David Gibson
2025-03-12 2:18 ` David Gibson [this message]
2025-03-12 2:18 ` [PATCH v2 5/9] packet: Remove redundant TAP_BUF_BYTES define David Gibson
2025-03-12 2:18 ` [PATCH v2 6/9] tap: Use explicit defines for maximum length of L2 frame David Gibson
2025-03-12 2:18 ` [PATCH v2 7/9] Simplify sizing of pkt_buf David Gibson
2025-03-12 2:18 ` [PATCH v2 8/9] pcap: Correctly set snaplen based on tap backend type David Gibson
2025-03-12 2:18 ` [PATCH v2 9/9] conf: Limit maximum MTU based on backend frame size David Gibson
2025-03-12 23:04 ` [PATCH v2 0/9] Improve handling of MTU limits Stefano Brivio
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=20250312021839.2405877-5-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).