mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srini@kernel.org>
To: "Tomasz Maciej Nowak" <tmn505@terefe.re>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"Srinivas Kandagatla" <srini@kernel.org>,
	linux-kernel@vger.kernel.org
Cc: Tomasz Maciej Nowak <tmn505@gmail.com>
Subject: Re: [PATCH v2] nvmem: layouts: u-boot-env: check earlier for ethaddr length
Date: Tue, 19 May 2026 16:55:30 +0100	[thread overview]
Message-ID: <6afd49c9-8389-4dfa-b1c5-c724d95019d5@kernel.org> (raw)
In-Reply-To: <20260504172103.18061-1-tmn505@terefe.re>



On 5/4/26 6:19 PM, Tomasz Maciej Nowak wrote:
> From: Tomasz Maciej Nowak <tmn505@gmail.com>
> 
> Unfortunately the ethaddr value in U-Boot environment might be enclosed
> in single/double quotes or be something completely different. This can
> make it different than MAC_ADDR_STR_LEN, which results in EINVAL
> returned by ethaddr post process. Move the check for length earlier,
> to skip post processing, so nvmem could still present ethaddr value as
> a string if the value doesn't match MAC_ADDR_STR_LEN.
> 
> Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
> ---
> 
> v2
> Better clarification in commit message
> 
> v1
> Link: https://lore.kernel.org/all/20260319171236.48325-1-tmn505@terefe.re/
> 
>  drivers/nvmem/layouts/u-boot-env.c | 5 +----
>  1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/drivers/nvmem/layouts/u-boot-env.c b/drivers/nvmem/layouts/u-boot-env.c
> index f27f387bb52a..dd3f541728bf 100644
> --- a/drivers/nvmem/layouts/u-boot-env.c
> +++ b/drivers/nvmem/layouts/u-boot-env.c
> @@ -38,9 +38,6 @@ static int u_boot_env_read_post_process_ethaddr(void *context, const char *id, i
>  {
>  	u8 mac[ETH_ALEN];
>  
> -	if (bytes != MAC_ADDR_STR_LEN)
> -		return -EINVAL;
> -
>  	if (!mac_pton(buf, mac))
>  		return -EINVAL;
>  
> @@ -75,7 +72,7 @@ static int u_boot_env_parse_cells(struct device *dev, struct nvmem_device *nvmem
>  		info.offset = data_offset + value - data;
>  		info.bytes = strlen(value);
>  		info.np = of_get_child_by_name(dev->of_node, info.name);
> -		if (!strcmp(var, "ethaddr")) {
> +		if ((!strcmp(var, "ethaddr")) && (info.bytes == MAC_ADDR_STR_LEN)) {

if (!strcmp(var, "ethaddr") && info.bytes == MAC_ADDR_STR_LEN)

instead?


>  			info.raw_len = strlen(value);
>  			info.bytes = ETH_ALEN;
>  			info.read_post_process = u_boot_env_read_post_process_ethaddr;


  reply	other threads:[~2026-05-19 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 17:19 Tomasz Maciej Nowak
2026-05-19 15:55 ` Srinivas Kandagatla [this message]
2026-05-19 19:57   ` tomek

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=6afd49c9-8389-4dfa-b1c5-c724d95019d5@kernel.org \
    --to=srini@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=tmn505@gmail.com \
    --cc=tmn505@terefe.re \
    /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

all inboxes | Powered by JetHome®