strfilter__or(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… strfilter__or β€” the kernel API manual, bestie edition πŸŽ€

okay so picture this: it's a strfilter__or(9) situation, straight out of the Kernel API Manual, and ngl it's a tiny little function that does one very specific iconic thing. let's get into it ✨


🌸 NAME 🌸

strfilter__or β€” appends one more rule to your filter, and it does it with a logical-or. that's it, that's the whole vibe πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

int strfilter__or (struct strfilter *filter , const char *rules , const
char **err );

look at her. three args, returns an int, no drama. slay πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • filter β€” the original string filter. this is your main character, the thing everything gets attached to πŸ‘‘
  • rules β€” the filter rule that's gonna get appended at the left of the root of filter, by using logical-or. yes, left, at the root β€” that's exactly what the man page says and i'm not about to paraphrase the address, periodt πŸ’…
  • err β€” a pointer which points at an error detected on rules. so if the rules are giving problems, this is where you find out 😭

πŸ’œ DESCRIPTION πŸ’œ

so what actually happens? strfilter__or parses rules and joins it to the filter by using logical-or. that's the whole job, and she does it well 🫢

returns 0 if success β€” happy ending, we love to see it 🌈 β€” or returns the error code if it's not. so like, check your return value, bestie, no cap πŸ’€


⭐ SEE ALSO ⭐

the kernel file ./tools/perf/util/strfilter.h, plus the whole friend group:

iykyk πŸ¦‹


lowkey unrelated but: this page comes from ./tools/perf/util and it's dated October 2026, and the page itself is strfilter__or(9) β€” so yeah, that's the whole source/version/date situation, noted and respectfully acknowledged πŸ§šπŸ’œ

k bye, go read strfilter__compare(9) next, mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from