public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Enrique Llorente <ellorent@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] dhcp: Remove option 255 length byte
Date: Wed, 12 Feb 2025 12:14:32 +1100	[thread overview]
Message-ID: <Z6v1-Ee--iYfl8Jw@zatzit> (raw)
In-Reply-To: <20250211111434.945152-1-ellorent@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

On Tue, Feb 11, 2025 at 12:14:34PM +0100, Enrique Llorente wrote:
> The option 255 (end of options) do not need the length byte, this change
> remove that allowing to have one extra byte at other dynamic options.
> 
> Signed-off-by: Enrique Llorente <ellorent@redhat.com>

Thanks, change is good.  However, could you also update the comment on
OPT_MAX's definition that appears to have the same error in it.

> ---
>  dhcp.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/dhcp.c b/dhcp.c
> index 401cb5b..3aef13f 100644
> --- a/dhcp.c
> +++ b/dhcp.c
> @@ -127,7 +127,7 @@ struct msg {
>  	uint8_t sname[64];
>  	uint8_t file[128];
>  	uint32_t magic;
> -	uint8_t o[OPT_MAX + 2 /* End option and its length */ ];
> +	uint8_t o[OPT_MAX + 1 /* End option */ ];
>  } __attribute__((__packed__));
>  
>  /**
> @@ -194,7 +194,6 @@ static int fill(struct msg *m)
>  	}
>  
>  	m->o[offset++] = 255;
> -	m->o[offset++] = 0;
>  
>  	if (offset < OPT_MIN) {
>  		memset(&m->o[offset], 0, OPT_MIN - offset);

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-02-12  1:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 11:14 [PATCH] dhcp: Remove option 255 length byte Enrique Llorente
2025-02-12  1:14 ` David Gibson [this message]
2025-02-12  1:38   ` Stefano Brivio
2025-02-17  9:24     ` Enrique Llorente Pastora

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=Z6v1-Ee--iYfl8Jw@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=ellorent@redhat.com \
    --cc=passt-dev@passt.top \
    /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).