diag_trigger_master_store(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ diag_trigger_master_store(9) πŸŽ€

okay so bestie, welcome to the kernel API manual ✨ this one lives in section 9 (the (9) in the name, iykyk) and it's literally all about diag_trigger_master_store β€” the function that stores the diag_trigger_master attribute πŸ’…


✨ NAME ✨

diag_trigger_master_store β€” store the diag_trigger_master attribute 🫢


🌸 SYNOPSIS 🌸

ssize_t diag_trigger_master_store (struct device *cdev , struct
       device_attribute *attr , const char *buf , size_t count );

that's the whole signature, no cap πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • cdev β€” pointer to embedded class device πŸ’–
  • attr β€” ? (yes, literally a question mark. the docs said ? and we're honoring it fr fr πŸ™ˆ)
  • buf β€” the buffer returned πŸŽ€
  • count β€” ? (again, a mystery. iconic of it honestly πŸ’€)

πŸ’œ DESCRIPTION πŸ’œ

A sysfs 'read/write' shost attribute ✨ that's the whole vibe check, bestie β€” nothing more to spill 🌈


πŸ”₯ SEE ALSO πŸ”₯

the kernel file lives at ./drivers/scsi/mpt3sas/mpt3sas_ctl.c, and here's the full squad that comes with it πŸ‘‘

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_do_mpt_command(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_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 entire friend group and every single one of them slays πŸ’…βœ¨


heads up bestie: that attr and count really are documented as ? in the original β€” not me being lazy, that's just the source material πŸ™ˆ no cap.

and that's the page!! 🫢 sourced from ./drivers/scsi/mpt3sas, dated October 2026 β€” mwah, go read some kernel code, ily, bye πŸ’–πŸŽ€βœ¨

πŸ“¦ where this page comes from