From: Michal Kubecek <mkubecek@suse.cz>
To: "Tomasz Moń" <tomasz.mon@camlingroup.com>
Cc: netdev@vger.kernel.org, "Andrew Lunn" <andrew@lunn.ch>,
"Krzysztof Drobiński" <k.drobinski@camlintechnologies.com>
Subject: Re: [PATCH ethtool v2] ethtool: fix EEPROM byte write
Date: Mon, 22 Aug 2022 01:28:11 +0200 [thread overview]
Message-ID: <20220821232811.a2dlidrm5i62n6yu@lion.mk-sys.cz> (raw)
In-Reply-To: <20220819101049.1939033-1-tomasz.mon@camlingroup.com>
[-- Attachment #1: Type: text/plain, Size: 2513 bytes --]
On Fri, Aug 19, 2022 at 12:10:49PM +0200, Tomasz Moń wrote:
> ethtool since version 1.8 supports EEPROM byte write:
> # ethtool -E DEVNAME [ magic N ] [ offset N ] [ value N ]
>
> ethtool 2.6.33 added EEPROM block write:
> # ethtool -E ethX [ magic N ] [ offset N ] [ length N ] [ value N ]
>
> EEPROM block write introduced in 2.6.33 is backwards compatible, i.e.
> when value is specified the length is forced to 1 (commandline length
> value is ignored).
>
> The byte write behaviour changed in ethtool 5.9 where the value write
> only works when value parameter is specified together with length 1.
> While byte writes to any offset other than 0, without length 1, simply
> fail with "offset & length out of bounds" error message, writing value
> to offset 0 basically erased whole EEPROM. That is, the provided byte
> value was written at offset 0, but the rest of the EEPROM was set to 0.
>
> Fix the issue by setting length to 1 when value is specified and length
> is omitted. Exit with error if length is specified to value other than 1
> and value is specified.
>
> Fixes: 923c3f51c444 ("ioctl: check presence of eeprom length argument properly")
> Signed-off-by: Tomasz Moń <tomasz.mon@camlingroup.com>
> ---
> changes in v2:
> - set the length to 1 only if not specified by user
> - exit with error if length is not 1
>
> v1: https://lore.kernel.org/netdev/20220819062933.1155112-1-tomasz.mon@camlingroup.com/
> ---
> ethtool.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/ethtool.c b/ethtool.c
> index 89613ca..7b400da 100644
> --- a/ethtool.c
> +++ b/ethtool.c
> @@ -3529,12 +3529,16 @@ static int do_seeprom(struct cmd_context *ctx)
> return 74;
> }
>
> - if (seeprom_value_seen)
> + if (seeprom_value_seen && !seeprom_length_seen)
> seeprom_length = 1;
> -
> - if (!seeprom_length_seen)
> + else if (!seeprom_length_seen)
> seeprom_length = drvinfo.eedump_len;
It would probably look a bit nicer like this:
if (!seeprom_length_seen)
seeprom_length = seeprom_value_seen ? 1 : drvinfo.eedump_len;
but that's just matter of taste so let's take it as it is.
Michal
>
> + if (seeprom_value_seen && (seeprom_length != 1)) {
> + fprintf(stderr, "value requires length 1\n");
> + return 1;
> + }
> +
> if (drvinfo.eedump_len < seeprom_offset + seeprom_length) {
> fprintf(stderr, "offset & length out of bounds\n");
> return 1;
> --
> 2.25.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-08-21 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 10:10 [PATCH ethtool v2] ethtool: fix EEPROM byte write Tomasz Moń
2022-08-21 23:20 ` patchwork-bot+netdevbpf
2022-08-21 23:28 ` Michal Kubecek [this message]
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=20220821232811.a2dlidrm5i62n6yu@lion.mk-sys.cz \
--to=mkubecek@suse.cz \
--cc=andrew@lunn.ch \
--cc=k.drobinski@camlintechnologies.com \
--cc=netdev@vger.kernel.org \
--cc=tomasz.mon@camlingroup.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox