zfcp_fsf_req_complete(9)

✨ zfcp_fsf_req_complete 💅

Okay bestie, so this is from the Kernel API Manual and it's all about zfcp_fsf_req_complete — literally the function that handles what happens when an FSF request is done-zo. No cap, it's giving "cleanup crew energy" and I'm obsessed 🎀

🌸 SYNOPSIS 🌸

void zfcp_fsf_req_complete (struct zfcp_fsf_req *req );

🦋 ARGUMENTS 🦋

• req — The FSF request that has been completed. Like, the one that just finished its whole journey, periodt 💖

✨ DESCRIPTION ✨

Okay so picture this: a request has been completed — either it came back from the FCP adapter, or it got dismissed because of a queue shutdown. Either way, this function gets called to process that completion status and trigger all the further events related to the FSF request. It's literally the main character of request completion 🫶

⚠️ Huge disclaimer bestie — the caller must ensure that the request has already been removed from adapter->req_list. This is non-negotiable, fr fr. Why? To protect against concurrent modification by zfcp_erp_strategy_check_fsfreq. Don't skip this step or you're gonna have a bad time 💀

🔥 SEE ALSO 🔥

The whole squad roll call, iykyk:

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

Alright bestie, that's the whole vibe. This page lives in ./drivers/s390/scsi and it's dated October 2026 — slay, iconic, we love a kernel doc with a timestamp. Go forth and complete those FSF requests responsibly 💜✨