_ctl_do_mpt_command(9)
π
_ctl_do_mpt_command β the main handler for the MPT3COMMAND opcode β¨
okay so first things first, bestie: this is a page from the Kernel API Manual (yes, the kernel has a manual, it's giving official π) and today's main character is _ctl_do_mpt_command. she's the one who handles the MPT3COMMAND opcode. no cap, that's literally her whole job title π
πΈ SYNOPSIS πΈ
long _ctl_do_mpt_command (struct MPT3SAS_ADAPTER *ioc , struct
mpt3_ioctl_command karg , void __user *mf );
like, she takes three things and returns a long. iconic signature fr fr π«Ά
β¨ ARGUMENTS β¨
iocβ the per adapter object π. that's your adapter's own little world, her whole personality.kargβ a(struct mpt3_ioctl_command). yes the type is in parens, we love a well-labeled parameter πmfβ a pointer tomf, and plot twist: thatmflives in user space π so like, be normal about it.
π¦ SEE ALSO π¦
okay this list is lowkey a whole friend group π everyone in it gets a (9) because they're all kernel API pages. the kernel file lives at ./drivers/scsi/mpt3sas/mpt3sas_ctl.c and honestly the roster is long, so buckle up buttercup:
enum block_state(9)_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_getiocinfo(9)_ctl_eventquery(9)_ctl_eventenable(9)_ctl_eventreport(9)_ctl_do_reset(9)_ctl_btdh_search_sas_device(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)
likeβ¦ that's the whole function family reunion and everyone showed up π every single _show and _store, all the diag stuff, all the btdh lookups, the compat twins, the mpt2 variants β nobody left out, periodt π
real talk though bestie: she's taking a pointer from user space (mf), so this is one of those "trust but verify" moments. handle with care, okay? π«Ά
and that's the page!! brought to you by the ./drivers/scsi/mpt3sas source tree, dated October 2026 β mwah, go read the whole friend group, iykyk ππ§ββοΈ
π¦ 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