get_thread_name(9)

💖 get_thread_name(9) — Kernel API Manual 💖

🌸 NAME 🌸

get_thread_name — formats the name of the worker thread you want to support a given work queue. That's the whole slay. It's giving “just name the thread, bestie.” ✨

🦋 SYNOPSIS 🦋

void get_thread_name (const struct thread_config *thread_config ,
       thread_id_t thread_id , char *buffer , size_t buffer_length );

🎀 ARGUMENTS 🎀

• thread_config — the thread configuration. Yep, the config for the thread. 💅
• thread_id — the thread ID. No cap.
• buffer — where to put the formatted name. This is the output spot, bestie. 🫶
• buffer_length — size of the output buffer. Respect the buffer’s boundaries, okay? 💖

🦋 DESCRIPTION 🦋

Okay so here’s the tea: the physical layer may add a prefix that identifies the product, but the output from this function should just identify the thread. So when you look at what comes out, it should be thread-identifying and that’s it. The product prefix is a physical-layer moment, not this function’s output era. Periodt. 🌸

💜 SEE ALSO 💜

Go have a little reading era, bestie. Here’s the whole squad, in order, all (9) and all iconic:

• Kernel file ./drivers/md/dm-vdo/vdo.c — Introduction(9), vdo_initialize_device_registry_once(9), filter_vdos_locked(9), vdo_find_matching(9), initialize_thread_config(9), vdo_make_thread(9)
• register_vdo(9), vdo_format(9), initialize_vdo(9), vdo_make(9), free_listeners(9), unregister_vdo(9)
• vdo_destroy(9), finish_reading_super_block(9), handle_super_block_read_error(9), vdo_load_super_block(9), vdo_get_backing_device(9), vdo_get_device_name(9)
• vdo_synchronous_flush(9), vdo_get_state(9), vdo_set_state(9), vdo_get_admin_state(9), record_vdo(9), continue_parent(9)
• handle_geometry_block_save_error(9), vdo_save_geometry_block(9), handle_super_block_save_error(9), vdo_save_super_block(9), vdo_save_components(9), vdo_register_read_only_listener(9)
• notify_vdo_of_read_only_mode(9), vdo_enable_read_only_entry(9), vdo_wait_until_not_entering_read_only_mode(9), as_notifier(9), finish_entering_read_only_mode(9), make_thread_read_only(9)
• vdo_allow_read_only_mode_entry(9), vdo_enter_read_only_mode(9), vdo_is_read_only(9), vdo_in_read_only_mode(9), vdo_in_recovery_mode(9), vdo_enter_recovery_mode(9)
• complete_synchronous_action(9), perform_synchronous_action(9), set_compression_callback(9), vdo_set_compressing(9), vdo_get_compressing(9), vdo_get_physical_blocks_allocated(9)
• vdo_get_physical_blocks_overhead(9), get_vdo_statistics(9), vdo_fetch_statistics_callback(9), vdo_fetch_statistics(9), vdo_get_callback_thread_id(9), vdo_dump_status(9)
• vdo_assert_on_admin_thread(9), vdo_assert_on_logical_zone_thread(9), vdo_assert_on_physical_zone_thread(9), vdo_get_physical_zone(9)

That’s the whole page, bestie. Source/version: ./drivers/md/dm-vdo; date: October 2026. Bye! 💖✨