zfcp_fsf_exc...ig_data_sync(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

zfcp_fsf_exchange_config_data_sync(9) β€” Kernel API Manual ✨

🌸 NAME 🌸

Okay bestie, meet zfcp_fsf_exchange_config_data_sync β€” the Kernel API Manual function that is literally here to Request information about FCP channel. πŸ’…


✨ SYNOPSIS ✨

int zfcp_fsf_exchange_config_data_sync (struct zfcp_qdio *qdio , struct
fsf_qtcb_bottom_config *data );

πŸ’– ARGUMENTS πŸ’–

  • qdio β€” pointer to the QDIO-Queue to use for sending the command. 🫢
  • data β€” pointer to the QTCB-Bottom for storing the result of the command, might be NULL. πŸ™ˆ

πŸ”₯ RETURN πŸ”₯

  • 0 β€” Exchange Config Data was successful, data is complete βœ…
  • -EIO β€” Exchange Config Data was not successful, data is invalid πŸ’€
  • -EAGAIN β€” data contains incomplete data 😭
  • -ENOMEM β€” Some memory allocation failed along the way 🫠

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/s390/scsi/zfcp_fsf.c β€” and the whole squad: zfcp_fsf_req_free(9), zfcp_fsf_req_complete(9), zfcp_fsf_req_dismiss_all(9), zfcp_fsf_scnprint_fc_security(9), zfcp_fsf_status_read(9), zfcp_fsf_abort_fcp_cmnd(9), zfcp_fsf_send_ct(9), zfcp_fsf_send_els(9), zfcp_fsf_exchange_port_data(9), zfcp_fsf_exchange_port_data_sync(9), zfcp_fsf_open_port(9), zfcp_fsf_close_port(9), zfcp_fsf_open_wka_port(9), zfcp_fsf_close_wka_port(9), zfcp_fsf_close_physical_port(9), zfcp_fsf_open_lun(9), zfcp_fsf_close_lun(9), zfcp_fsf_fcp_handler_common(9), zfcp_fsf_fcp_cmnd(9), zfcp_fsf_fcp_task_mgmt(9), zfcp_fsf_reqid_check(9).


mwah πŸ’‹ sign-off time: source/version is ./drivers/s390/scsi, date is October 2026, and this is the Kernel API Manual β€” iconic, no cap. πŸŽ€

πŸ“¦ where this page comes from