From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Mahe Tardy <mahe.tardy@gmail.com>, bpf@vger.kernel.org
Cc: andrii@kernel.org, yatsenko@meta.com, daniel@iogearbox.net,
john.fastabend@gmail.com
Subject: Re: [PATCH bpf-next] selftests/bpf: fix veristat comp mode with new stats
Date: Fri, 20 Dec 2024 15:40:28 +0000 [thread overview]
Message-ID: <3187e279-71c6-42df-9344-23275c81d79e@gmail.com> (raw)
In-Reply-To: <20241220152218.28405-1-mahe.tardy@gmail.com>
On 20/12/2024 15:22, Mahe Tardy wrote:
> Commit 82c1f13de315 ("selftests/bpf: Add more stats into veristat")
> introduced new stats, added by default in the CSV output, that were not
> added to parse_stat_value, used in parse_stats_csv which is used in
> comparison mode. Thus it broke comparison mode altogether making it fail
> with "Unrecognized stat #7" and EINVAL.
>
> One quirk is that PROG_TYPE and ATTACH_TYPE have been transformed to
> strings using libbpf_bpf_prog_type_str and libbpf_bpf_attach_type_str
> respectively. Since we might not want to compare those string values, we
> just skip the parsing in this patch. We might want to translate it back
> to the enum value or compare the string value directly.
>
> Signed-off-by: Mahe Tardy <mahe.tardy@gmail.com>
> ---
> tools/testing/selftests/bpf/veristat.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/bpf/veristat.c b/tools/testing/selftests/bpf/veristat.c
> index 9d17b4dfc170..476bf95cf684 100644
> --- a/tools/testing/selftests/bpf/veristat.c
> +++ b/tools/testing/selftests/bpf/veristat.c
> @@ -1672,7 +1672,10 @@ static int parse_stat_value(const char *str, enum stat_id id, struct verif_stats
> case TOTAL_STATES:
> case PEAK_STATES:
> case MAX_STATES_PER_INSN:
> - case MARK_READ_MAX_LEN: {
> + case MARK_READ_MAX_LEN:
> + case SIZE:
> + case JITED_SIZE:
> + case STACK: {
> long val;
> int err, n;
>
> @@ -1685,6 +1688,9 @@ static int parse_stat_value(const char *str, enum stat_id id, struct verif_stats
> st->stats[id] = val;
> break;
> }
> + case PROG_TYPE:
> + case ATTACH_TYPE:
> + break;
> default:
> fprintf(stderr, "Unrecognized stat #%d\n", id);
> return -EINVAL;
> --
> 2.34.1
>
Looks good, thanks!
Tested-by: Mykyta Yatsenko<yatsenko@meta.com>
next prev parent reply other threads:[~2024-12-20 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 15:22 [PATCH bpf-next] selftests/bpf: fix veristat comp mode with new stats Mahe Tardy
2024-12-20 15:40 ` Mykyta Yatsenko [this message]
2024-12-30 23:00 ` patchwork-bot+netdevbpf
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=3187e279-71c6-42df-9344-23275c81d79e@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=mahe.tardy@gmail.com \
--cc=yatsenko@meta.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