zfcp_fsf_exc...rt_data_sync(9)

💖 NAME 💖

okay bestie, this is the Kernel API Manual page for zfcp_fsf_exchange_port_data_sync(9) — and yes, the header up top is serving the truncated zfcp_fsf_exc...rt_data_sync(9) realness 🫶.

The NAME line is literally zfcp_fsf_exchange_port_data_sync - Request information about local port. — iconic, honestly ✨.

✨ SYNOPSIS ✨

int zfcp_fsf_exchange_port_data_sync (struct zfcp_qdio *qdio , struct
       fsf_qtcb_bottom_port *data );

🎀 ARGUMENTS 🎀

• qdio — pointer to the QDIO-Queue to use for sending the command. That's the queue bestie, the whole transport vibe. 💅
• data — pointer to the QTCB-Bottom for storing the result of the command, might be NULL. Yes, it can be NULL — no pressure 🫶.

🌸 RETURN 🌸

• 0 — Exchange Port Data was successful, data is complete. slay, full data, no crumbs ✨
• -EIO — Exchange Port Data was not successful, data is invalid. oop, invalid data, we don't love that 😭
• -EAGAIN — data contains incomplete data. half-finished data is giving unfinished homework tbh 💀
• -ENOMEM — Some memory allocation failed along the way. memory said "not today" 🙈
• -EOPNOTSUPP — This operation is not supported. not supported, not the vibe, moving on 💅

🦋 SEE ALSO 🦋

• Kernel file ./drivers/s390/scsi/zfcp_fsf.c
• 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_config_data_sync(9)
• zfcp_fsf_exchange_port_data(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)

that's the whole page, bestie 💖 — source/version: ./drivers/s390/scsi, date: October 2026, and the footer still says zfcp_fsf_exc...rt_data_sync(9). byeee, mwah 🎀✨