_ctl_btdh_search_sas_device(9)
π _ctl_btdh_search_sas_device β searching for sas device
okay so bestie, this one's from the Kernel API Manual, section 9 (the kernel API pages, iykyk), and it's a tiny little function page but we're gonna treat it with the respect it deserves π no cap, every argument, every cross-reference, all of it stays.
β¨ NAME β¨
_ctl_btdh_search_sas_device β searching for sas device
like, literally that's the whole job description π it goes looking for a sas device, and that's the vibe.
πΈ SYNOPSIS πΈ
int _ctl_btdh_search_sas_device (struct MPT3SAS_ADAPTER *ioc , struct
mpt3_ioctl_btdh_mapping *btdh );
it returns an int, takes two pointers, and yes the line break in the middle is exactly how it's written, don't come for me π
π¦ ARGUMENTS π¦
iocβ per adapter object π this is thestruct MPT3SAS_ADAPTER *for whichever adapter you're poking at, the main character of the whole driver fr fr.btdhβ btdh ioctl payload β¨ astruct mpt3_ioctl_btdh_mapping *, aka the payload riding along with the btdh ioctl. it's giving "envelope with the actual request inside" π
π₯ SEE ALSO π₯
okay so this is the part where the manpage just,,, lists its entire friend group π and we are NOT skipping a single one of them, periodt. the kernel file that started it all:
- Kernel file
./drivers/scsi/mpt3sas/mpt3sas_ctl.c enum block_state(9)
and now the whole group chat π:
_ctl_display_some_debug(9)mpt3sas_ctl_done(9)_ctl_check_event_type(9)mpt3sas_ctl_add_to_event_log(9)mpt3sas_ctl_event_callback(9)_ctl_verify_adapter(9)mpt3sas_ctl_pre_reset_handler(9)mpt3sas_ctl_clear_outstanding_ioctls(9)mpt3sas_ctl_reset_done_handler(9)_ctl_fasync(9)_ctl_poll(9)_ctl_set_task_mid(9)_ctl_send_mctp_passthru_req(9)_ctl_do_mpt_command(9)_ctl_getiocinfo(9)_ctl_eventquery(9)_ctl_eventenable(9)_ctl_eventreport(9)_ctl_do_reset(9)_ctl_btdh_search_pcie_device(9)_ctl_btdh_search_raid_device(9)_ctl_btdh_mapping(9)_ctl_diag_capability(9)_ctl_diag_get_bufftype(9)_ctl_diag_register_2(9)mpt3sas_enable_diag_buffer(9)_ctl_diag_register(9)_ctl_diag_unregister(9)_ctl_diag_query(9)mpt3sas_send_diag_release(9)_ctl_diag_release(9)_ctl_diag_read_buffer(9)_ctl_addnl_diag_query(9)_ctl_enable_diag_sbr_reload(9)_ctl_compat_mpt_command(9)_ctl_ioctl_main(9)_ctl_get_mpt_mctp_passthru_adapter(9)mpt3sas_get_device_count(9)_ctl_ioctl(9)_ctl_mpt2_ioctl(9)_ctl_ioctl_compat(9)_ctl_mpt2_ioctl_compat(9)version_fw_show(9)version_bios_show(9)version_mpi_show(9)version_product_show(9)version_nvdata_persistent_show(9)version_nvdata_default_show(9)board_name_show(9)board_assembly_show(9)board_tracer_show(9)io_delay_show(9)device_delay_show(9)fw_queue_depth_show(9)host_sas_address_show(9)logging_level_show(9)fwfault_debug_show(9)ioc_reset_count_show(9)reply_queue_count_show(9)BRM_status_show(9)host_trace_buffer_size_show(9)host_trace_buffer_show(9)host_trace_buffer_enable_show(9)diag_trigger_master_show(9)diag_trigger_master_store(9)diag_trigger_event_show(9)diag_trigger_event_store(9)diag_trigger_scsi_show(9)diag_trigger_scsi_store(9)diag_trigger_mpi_show(9)diag_trigger_mpi_store(9)drv_support_bitmap_show(9)enable_sdev_max_qd_show(9)enable_sdev_max_qd_store(9)sas_address_show(9)sas_device_handle_show(9)sas_ncq_prio_supported_show(9)sas_ncq_prio_enable_show(9)mpt3sas_ctl_init(9)mpt3sas_ctl_release(9)mpt3sas_ctl_exit(9)
that's the whole list, untouched, no edits, no "and friends", because leaving one out would be a crime and we don't do crimes here π
aaaand that's the page!! π«Ά this little cutie lives under ./drivers/scsi/mpt3sas and the date stamped on it is October 2026, still signed _ctl_btdh_search_sas_device(9) at the bottom like a little signature. go read your kernel source bestie, it ate π
β
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms