From: Anshu Kumari <anskuma@redhat.com>
To: anskuma@redhat.com, sbrivio@redhat.com, passt-dev@passt.top
Cc: lvivier@redhat.com, david@gibson.dropbear.id.au, jmaloy@redhat.com
Subject: [PATCH v5 1/7] dhcp: Refactor fill_one() to operate on a generic buffer
Date: Fri, 17 Jul 2026 23:26:38 +0530 [thread overview]
Message-ID: <20260717175648.879152-2-anskuma@redhat.com> (raw)
In-Reply-To: <20260717175648.879152-1-anskuma@redhat.com>
Change fill_one() to accept a buffer pointer and capacity instead of
a struct msg pointer. This is a pure refactor with no behavior change,
preparing for option overload support where fill_one() will also write
into the file and sname fields.
Link: https://bugs.passt.top/show_bug.cgi?id=192
Signed-off-by: Anshu Kumari <anskuma@redhat.com>
---
v5:
- Restore debug messages for skipped options in fill()
- Add /* code and length of option */ comment in size check
- Use buf + *offset instead of &buf[*offset] for memcpy
v3:
- Restored removed comments: "If we don't have space to write the
option, then just skip" and "Move to option".
v2:
- Renamed parameter cap → size.
---
dhcp.c | 27 ++++++++++++++-------------
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/dhcp.c b/dhcp.c
index c3c7422..bb72b72 100644
--- a/dhcp.c
+++ b/dhcp.c
@@ -131,28 +131,29 @@ struct msg {
} __attribute__((__packed__));
/**
- * fill_one() - Fill a single option in message
- * @m: Message to fill
+ * fill_one() - Fill a single option into a buffer
+ * @buf: Buffer to write option
+ * @size: Usable size of @buf (excluding end marker)
* @o: Option number
- * @offset: Current offset within options field, updated on insertion
+ * @offset: Current offset within @buf, updated on insertion
*
- * Return: false if m has space to write the option, true otherwise
+ * Return: false if @buf has space to write the option, true otherwise
*/
-static bool fill_one(struct msg *m, int o, int *offset)
+static bool fill_one(uint8_t *buf, size_t size, int o, int *offset)
{
size_t slen = opts[o].slen;
/* If we don't have space to write the option, then just skip */
- if (*offset + 2 /* code and length of option */ + slen > OPT_MAX)
+ if (*offset + 2 /* code and length of option */ + slen > size)
return true;
- m->o[*offset] = o;
- m->o[*offset + 1] = slen;
+ buf[*offset] = o;
+ buf[*offset + 1] = slen;
/* Move to option */
*offset += 2;
- memcpy(&m->o[*offset], opts[o].s, slen);
+ memcpy(buf + *offset, opts[o].s, slen);
opts[o].sent = 1;
*offset += slen;
@@ -177,19 +178,19 @@ static int fill(struct msg *m)
* Put it there explicitly, unless requested via option 55.
*/
if (opts[55].clen > 0 && !memchr(opts[55].c, 53, opts[55].clen))
- if (fill_one(m, 53, &offset))
- debug("DHCP: skipping option 53");
+ if (fill_one(m->o, OPT_MAX, 53, &offset))
+ debug("DHCP: skipping option 53");
for (i = 0; i < opts[55].clen; i++) {
o = opts[55].c[i];
if (opts[o].slen != -1)
- if (fill_one(m, o, &offset))
+ if (fill_one(m->o, OPT_MAX, o, &offset))
debug("DHCP: skipping option %i", o);
}
for (o = 0; o < 255; o++) {
if (opts[o].slen != -1 && !opts[o].sent)
- if (fill_one(m, o, &offset))
+ if (fill_one(m->o, OPT_MAX, o, &offset))
debug("DHCP: skipping option %i", o);
}
--
2.54.0
next prev parent reply other threads:[~2026-07-17 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 17:56 [PATCH v5 0/7] Add --dhcp-boot and --dhcp-opt options Anshu Kumari
2026-07-17 17:56 ` Anshu Kumari [this message]
2026-07-17 17:56 ` [PATCH v5 2/7] dhcp: Add option state management with enum opt_state Anshu Kumari
2026-07-17 17:56 ` [PATCH v5 3/7] dhcp: Add option overload Anshu Kumari
2026-07-17 17:56 ` [PATCH v5 4/7] dhcp: Add --dhcp-opt with option table and value parser Anshu Kumari
2026-07-17 17:56 ` [PATCH v5 5/7] dhcp: Add --dhcp-boot command-line option Anshu Kumari
2026-07-17 17:56 ` [PATCH v5 6/7] dhcp: Add RFC 3396 option splitting for concatenation-requiring options Anshu Kumari
2026-07-17 17:56 ` [PATCH v5 7/7] dhcp: Handle FQDN option with RFC 3396 concatenation Anshu Kumari
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=20260717175648.879152-2-anskuma@redhat.com \
--to=anskuma@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=lvivier@redhat.com \
--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).