linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Petr Zejdl <petr.zejdl@cern.ch>
Cc: "David S. Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: ipv4: ipconfig: Support RFC 4361/3315 DHCP client ID in hex format
Date: Thu, 12 Jun 2025 19:17:26 -0700	[thread overview]
Message-ID: <20250612191726.2a226cdf@kernel.org> (raw)
In-Reply-To: <20250610143504.731114-1-petr.zejdl@cern.ch>

On Tue, 10 Jun 2025 16:35:03 +0200 Petr Zejdl wrote:
> -		len = strlen(dhcp_client_identifier + 1);

maybe keep using len here? Assign dhcp_client_identifier_len to it?
I don't think switching to dhcp_client_identifier_len improves the
readability and it inflates the diff.

>  		/* the minimum length of identifier is 2, include 1 byte type,
>  		 * and can not be larger than the length of options
>  		 */
> -		if (len >= 1 && len < 312 - (e - options) - 1) {
> -			*e++ = 61;
> -			*e++ = len + 1;
> -			memcpy(e, dhcp_client_identifier, len + 1);
> -			e += len + 1;
> +		if (dhcp_client_identifier_len >= 2) {
> +			if (dhcp_client_identifier_len <= 312 - (e - options) - 3) {
> +				pr_debug("DHCP: sending client identifier %*phC\n",
> +					 dhcp_client_identifier_len,
> +					 dhcp_client_identifier);
> +				*e++ = 61;
> +				*e++ = dhcp_client_identifier_len;
> +				memcpy(e, dhcp_client_identifier,
> +				       dhcp_client_identifier_len);
> +				e += dhcp_client_identifier_len;
> +			} else {
> +				pr_warn("DHCP: client identifier doesn't fit in the packet\n");
> +			}
>  		}
>  	}
>  
> @@ -1661,6 +1669,33 @@ static int __init ip_auto_config(void)
>  
>  late_initcall(ip_auto_config);
>  
> +#ifdef CONFIG_IP_PNP_DHCP
> +/*
> + *  Parses DHCP Client ID in the hex form "XX:XX ... :XX" (like MAC address).
> + *  Returns the length (min 2, max 253) or -EINVAL on parsing error.
> + */
> +static int __init parse_client_id(const char *s, u8 *buf)
> +{
> +	int slen = strlen(s);
> +	int len = (slen + 1) / 3;
> +	int i;
> +
> +	/* Format: XX:XX ... :XX */
> +	if (len * 3 - 1 != slen || len < 2 || len > 253)
> +		return -EINVAL;
> +
> +	for (i = 0; i < len; i++) {
> +		if (!isxdigit(s[i * 3]) || !isxdigit(s[i * 3 + 1]))
> +			return -EINVAL;
> +		if (i != len - 1 && s[i * 3 + 2] != ':')
> +			return -EINVAL;
> +
> +		buf[i] = (hex_to_bin(s[i * 3]) << 4) | hex_to_bin(s[i * 3 + 1]);
> +	}
> +
> +	return i;
> +}

Feels like this helper should live in lib/net_utils.c or lib/hexdump.c
as a generic thing?
-- 
pw-bot: cr

  reply	other threads:[~2025-06-13  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 14:35 [PATCH] net: ipv4: ipconfig: Support RFC 4361/3315 DHCP client ID in hex format Petr Zejdl
2025-06-13  2:17 ` Jakub Kicinski [this message]
2025-06-13 22:37   ` Petr Zejdl

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=20250612191726.2a226cdf@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petr.zejdl@cern.ch \
    /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).