From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, jose.marchesi@oracle.com
Subject: Re: [RFC bpf-next v1 5/8] selftests/bpf: no need to track next_match_pos in struct test_loader
Date: Tue, 02 Jul 2024 14:05:38 -0700 [thread overview]
Message-ID: <1e6f66cc6bcd80cc636206b5948c3a03e455711a.camel@gmail.com> (raw)
In-Reply-To: <CAEf4BzYeAG7SFschgypp3WHcQ2B4uxY4-euiU_pXM4s9dfHKNA@mail.gmail.com>
On Mon, 2024-07-01 at 17:41 -0700, Andrii Nakryiko wrote:
[...]
> > static void emit_verifier_log(const char *log_buf, bool force)
> > @@ -450,23 +449,23 @@ static void validate_case(struct test_loader *tester,
> > struct bpf_program *prog,
> > int load_err)
> > {
> > - int i, j, err;
> > - char *match;
> > regmatch_t reg_match[1];
> > + const char *match;
> > + const char *log = tester->log_buf;
> > + int i, j, err;
> >
> > for (i = 0; i < subspec->expect_msg_cnt; i++) {
> > struct expect_msg *msg = &subspec->expect_msgs[i];
> >
> > if (msg->substr) {
> > - match = strstr(tester->log_buf + tester->next_match_pos, msg->substr);
> > + match = strstr(log, msg->substr);
> > if (match)
> > - tester->next_match_pos = match - tester->log_buf + strlen(msg->substr);
> > + log += strlen(msg->substr);
> > } else {
> > - err = regexec(&msg->regex,
> > - tester->log_buf + tester->next_match_pos, 1, reg_match, 0);
> > + err = regexec(&msg->regex, log, 1, reg_match, 0);
> > if (err == 0) {
> > - match = tester->log_buf + tester->next_match_pos + reg_match[0].rm_so;
> > - tester->next_match_pos += reg_match[0].rm_eo;
> > + match = log + reg_match[0].rm_so;
> > + log += reg_match[0].rm_eo;
>
> invert and simplify:
>
> log += reg_match[0].rm_eo;
> match = log;
>
> ?
The 'match' is at 'log + rm_so' (start offset).
The 'log' is at 'log + rm_eo' (end offset).
The brilliance of standard library naming.
>
> > } else {
> > match = NULL;
> > }
>
> how about we move this to the beginning of iteration (before `if
> (msg->substr)`) and so we'll assume the match is NULL on regexec
> failing?
Ok, but this would require explicit match re-initialization to NULL at
each iteration.
[...]
next prev parent reply other threads:[~2024-07-02 21:05 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 9:47 [RFC bpf-next v1 0/8] no_caller_saved_registers attribute for helper calls Eduard Zingerman
2024-06-29 9:47 ` [RFC bpf-next v1 1/8] bpf: add a get_helper_proto() utility function Eduard Zingerman
2024-07-02 0:41 ` Andrii Nakryiko
2024-07-02 20:07 ` Eduard Zingerman
2024-06-29 9:47 ` [RFC bpf-next v1 2/8] bpf: no_caller_saved_registers attribute for helper calls Eduard Zingerman
2024-07-01 19:01 ` Eduard Zingerman
2024-07-02 0:41 ` Andrii Nakryiko
2024-07-02 20:38 ` Eduard Zingerman
2024-07-02 21:09 ` Andrii Nakryiko
2024-07-02 21:19 ` Eduard Zingerman
2024-07-02 21:22 ` Andrii Nakryiko
2024-07-03 11:57 ` Puranjay Mohan
2024-07-03 16:13 ` Eduard Zingerman
2024-07-04 10:55 ` Puranjay Mohan
2024-06-29 9:47 ` [RFC bpf-next v1 3/8] bpf, x86: no_caller_saved_registers for bpf_get_smp_processor_id() Eduard Zingerman
2024-07-02 0:41 ` Andrii Nakryiko
2024-07-02 20:43 ` Eduard Zingerman
2024-07-02 21:11 ` Andrii Nakryiko
2024-07-02 21:25 ` Eduard Zingerman
2024-07-03 11:27 ` Puranjay Mohan
2024-07-03 23:14 ` Eduard Zingerman
2024-07-04 11:19 ` Puranjay Mohan
2024-07-04 16:39 ` Eduard Zingerman
2024-07-04 17:00 ` Eduard Zingerman
2024-07-04 17:24 ` Puranjay Mohan
2024-07-04 17:39 ` Eduard Zingerman
2024-06-29 9:47 ` [RFC bpf-next v1 4/8] selftests/bpf: extract utility function for BPF disassembly Eduard Zingerman
2024-07-02 0:41 ` Andrii Nakryiko
2024-07-02 20:59 ` Eduard Zingerman
2024-07-02 21:16 ` Andrii Nakryiko
2024-07-02 21:23 ` Eduard Zingerman
2024-06-29 9:47 ` [RFC bpf-next v1 5/8] selftests/bpf: no need to track next_match_pos in struct test_loader Eduard Zingerman
2024-07-02 0:41 ` Andrii Nakryiko
2024-07-02 21:05 ` Eduard Zingerman [this message]
2024-07-02 21:18 ` Andrii Nakryiko
2024-06-29 9:47 ` [RFC bpf-next v1 6/8] selftests/bpf: extract test_loader->expect_msgs as a data structure Eduard Zingerman
2024-07-02 0:42 ` Andrii Nakryiko
2024-07-02 21:06 ` Eduard Zingerman
2024-06-29 9:47 ` [RFC bpf-next v1 7/8] selftests/bpf: allow checking xlated programs in verifier_* tests Eduard Zingerman
2024-07-02 0:42 ` Andrii Nakryiko
2024-07-02 21:07 ` Eduard Zingerman
2024-07-02 21:19 ` Andrii Nakryiko
2024-06-29 9:47 ` [RFC bpf-next v1 8/8] selftests/bpf: test no_caller_saved_registers spill/fill removal Eduard Zingerman
2024-07-02 0:42 ` Andrii Nakryiko
2024-07-02 21:12 ` Eduard Zingerman
2024-07-02 21:20 ` Andrii Nakryiko
2024-07-02 0:41 ` [RFC bpf-next v1 0/8] no_caller_saved_registers attribute for helper calls Andrii Nakryiko
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=1e6f66cc6bcd80cc636206b5948c3a03e455711a.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jose.marchesi@oracle.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yonghong.song@linux.dev \
/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