]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
selftests/bpf: correctly move 'log' upon successful match
authorEduard Zingerman <eddyz87@gmail.com>
Tue, 20 Aug 2024 10:23:50 +0000 (03:23 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 4 Oct 2024 14:33:24 +0000 (16:33 +0200)
commit d0a29cdb6ef95d8a175e09ab2d1334271f047e60 upstream.

Suppose log="foo bar buz" and msg->substr="bar".
In such case current match processing logic would update 'log' as
follows: log += strlen(msg->substr); -> log += 3 -> log=" bar".
However, the intent behind the 'log' update is to make it point after
the successful match, e.g. to make log=" buz" in the example above.

Fixes: 4ef5d6af4935 ("selftests/bpf: no need to track next_match_pos in struct test_loader")
Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
Link: https://lore.kernel.org/r/20240820102357.3372779-3-eddyz87@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
tools/testing/selftests/bpf/test_loader.c

index 0f59bc33a666cac9f26616e1692df50f39581e3a..2150e9c9b53fb1e4a52cd70d395e06f3a83533ac 100644 (file)
@@ -545,7 +545,7 @@ static void validate_msgs(char *log_buf, struct expected_msgs *msgs,
                if (msg->substr) {
                        match = strstr(log, msg->substr);
                        if (match)
-                               log += strlen(msg->substr);
+                               log = match + strlen(msg->substr);
                } else {
                        err = regexec(&msg->regex, log, 1, reg_match, 0);
                        if (err == 0) {