tomoyo_file_...hes_pattern2(9)

💖 NAME 💖

okay so bestie, this is the tomoyo_file_...hes_pattern2(9) page from the Kernel API Manual — and the NAME is giving:

Pattern matching without '/' character and "-" pattern.

no cap, that's the assignment: pattern matching without the slash character and without the dash pattern 💅

✨ SYNOPSIS ✨

the signature, literally character-for-character:

bool tomoyo_file_matches_pattern2 (const char *filename , const char *filename_end , const char *pattern , const char *pattern_end );

💅 ARGUMENTS 💅

• filename — the start of string to check. yes, the beginning bestie 💖
• filename_end — the end of string to check.
• pattern — the start of pattern to compare.
• pattern_end — the end of pattern to compare.

that's the whole arg squad, all four of them, no cap 🫶

🦋 DESCRIPTION 🦋

Returns true if filename matches pattern, false otherwise.

That's the vibe check: match = true, no match = false. No extra lore, just true-or-false pattern-matching realness. 😭

🌸 SEE ALSO 🌸

Kernel file ./security/tomoyo/util.c — and the whole SEE ALSO squad is:

• tomoyo_convert_time(9)
• tomoyo_permstr(9)
• tomoyo_read_token(9)
• tomoyo_get_domainname(9)
• tomoyo_parse_ulong(9)
• tomoyo_print_ulong(9)
• tomoyo_parse_name_union(9)
• tomoyo_parse_number_union(9)
• tomoyo_byte_range(9)
• tomoyo_alphabet_char(9)
• tomoyo_make_byte(9)
• tomoyo_valid(9)
• tomoyo_invalid(9)
• tomoyo_str_starts(9)
• tomoyo_normalize_line(9)
• tomoyo_correct_word2(9)
• tomoyo_correct_word(9)
• tomoyo_correct_path2(9)
• tomoyo_correct_path(9)
• tomoyo_correct_domain(9)
• tomoyo_domain_def(9)
• tomoyo_find_domain(9)
• tomoyo_const_part_length(9)
• tomoyo_fill_path_info(9)
• tomoyo_file_matches_pattern(9)
• tomoyo_path_matches_pattern2(9)
• tomoyo_path_matches_pattern(9)
• tomoyo_get_exe(9)
• tomoyo_get_mode(9)
• tomoyo_init_request_info(9)
• tomoyo_domain_quota_is_ok(9)

mwah 💖 source/version: ./security/tomoyo · date: October 2026 · title: tomoyo_file_...hes_pattern2(9) — footer folded into this cute sign-off, byeee 🫶✨