tomoyo_print_ulong(9)

✨ NAME ✨

okay bestie, you're in the Kernel API Manual and this is the page for tomoyo_print_ulong(9) — it prints an "unsigned long" value. no cap, that's the whole name vibe. 💖

🌸 SYNOPSIS 🌸

highkey important, so here's the signature exactly:

void tomoyo_print_ulong (char *buffer , const int buffer_len , const unsigned long value , const u8 type );

🎀 ARGUMENTS 🎀

let's do a lil vibe check on the parameters, bestie:

• buffer — pointer to buffer. it's the spot where the output goes, main character location and all. ✨
• buffer_len — size of buffer. literally how much room you're handing over, so don't skip it, fr fr.
• value — an "unsigned long" value. the actual number in question, the moment itself.
• type — type of value. it's giving "what kind of value is this," iykyk. 🦋

🦋 DESCRIPTION 🦋

Returns nothing. yep, that's it — this one is a void, so there's no return value to catch, no status to chase, not even a little souvenir. it does its print thing and dips. periodt. 💅

👑 SEE ALSO 👑

Kernel file ./security/tomoyo/util.c, plus all these iconique friends — every single one is here, bestie, no skipping:

• tomoyo_convert_time(9)
• tomoyo_permstr(9)
• tomoyo_read_token(9)
• tomoyo_get_domainname(9)
• tomoyo_parse_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_pattern2(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)

that's the tea from ./security/tomoyo, dated October 2026 — tomoyo_print_ulong(9) out. 💖