All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: bot+bpf-ci@kernel.org, bpf@vger.kernel.org, ast@kernel.org,
	andrii@kernel.org
Cc: daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
	 yonghong.song@linux.dev, memxor@gmail.com,
	martin.lau@kernel.org, clm@meta.com, 	ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next 1/2] selftests/bpf: fix for veristat file/prog filters processing
Date: Tue, 11 Aug 2026 12:24:46 -0700	[thread overview]
Message-ID: <5da4529bb3a41a612f05b5d2dfc6b50f76ae03a8.camel@gmail.com> (raw)
In-Reply-To: <1b98af79fa5ac4a50f74eb67b30fecba06a9990d9483fdead77176412536fda0@mail.kernel.org>

On Tue, 2026-08-11 at 18:41 +0000, bot+bpf-ci@kernel.org wrote:
> >     selftests/bpf: fix for veristat file/prog filters processing
> > 
> >     At the moment veristat filtering behaves unexpectedly for the
> >     following filter expression:
> > 
> >       -f !file/prog
> > 
> >     The expression rejects all programs with name 'prog', and all programs
> >     in a file with name 'file'. This commit fixes the expression to
> >     exclude only a program 'prog' from a file 'file'. Additionally,
> >     the commit makes empty filters like '-f ""' or '-f "/"' and error.
> >     Here is the filtering behaviour compared old versus new:
> > 
> >     | filter   | file | prog | old verdict | new verdict |
> >     |----------+------+------+-------------+-------------|
> >     | !foo     | foo  | bar  | skipped     | skipped     |
> >     | !foo     | bar  | foo  | skipped     | skipped     |
> >     | !foo/bar | foo  | bar  | skipped     | skipped     |
> >     | !foo/bar | foo  | buz  | skipped     | processed   | (!)
> >     | !foo/bar | bar  | bar  | skipped     | processed   | (!)
> >     | !foo/    | foo  | bar  | skipped     | skipped     |
> >     | !foo/    | bar  | bar  | processed   | processed   |
> >     | !/bar    | foo  | bar  | skipped     | skipped     |
> >     | !/bar    | foo  | foo  | processed   | processed   |
> >     | !/       | foo  | bar  | processed   | error       | (!)
> >     | !        | foo  | bar  | processed   | error       | (!)
> >     |----------+------+------+-------------+-------------|
> >     | foo      | foo  | bar  | processed   | processed   |
> >     | foo      | bar  | foo  | processed   | processed   |
> >     | foo/bar  | foo  | bar  | processed   | processed   |
> >     | foo/bar  | foo  | buz  | skipped     | skipped     |
> >     | foo/bar  | bar  | bar  | skipped     | skipped     |
> >     | foo/     | foo  | bar  | processed   | processed   |
> >     | foo/     | bar  | bar  | skipped     | skipped     |
> >     | /bar     | foo  | bar  | processed   | processed   |
> >     | /bar     | foo  | foo  | skipped     | skipped     |
> >     | /        | foo  | bar  | processed   | error       | (!)
> >     |          | foo  | bar  | skipped     | error       | (!)
> > 
> >     Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
> 
> This looks like a bug fix for existing tooling. The changelog table marks
> four behavior rows with '(!)', showing the OR-matching bug being fixed and
> empty filters now being rejected. Should this include a Fixes: tag?
> 
> The broken semantics - deny filter matching on file OR prog independently,
> and empty filters being silently accepted - were introduced when the separate
> should_process_file() and should_process_prog() helpers were merged into
> should_process_file_prog():
> 
>   Fixes: 10b1b3f3e56a ("selftests/bpf: consolidate and improve file/prog filtering in veristat")
> 

Yeah, fixes tag should be added.

  reply	other threads:[~2026-08-11 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 17:52 [PATCH bpf-next 0/2] selftests/bpf: fix for veristat file/prog filters processing Eduard Zingerman
2026-08-11 17:52 ` [PATCH bpf-next 1/2] " Eduard Zingerman
2026-08-11 18:41   ` bot+bpf-ci
2026-08-11 19:24     ` Eduard Zingerman [this message]
2026-08-11 17:52 ` [PATCH bpf-next 2/2] selftests/bpf: exercise veristat filtering logic in a selftest Eduard Zingerman
2026-08-11 18:56   ` bot+bpf-ci
2026-08-11 19:29     ` Eduard Zingerman

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=5da4529bb3a41a612f05b5d2dfc6b50f76ae03a8.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bot+bpf-ci@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=clm@meta.com \
    --cc=daniel@iogearbox.net \
    --cc=ihor.solodrai@linux.dev \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.