fc_fcp_pkt_destroy(9)

💖 fc_fcp_pkt_destroy(9) 💖

Okay bestie, welcome to the Kernel API Manual page for fc_fcp_pkt_destroy(9) — yes, the title and manual name are right there, we're doing this properly. Let's get into it 💅

✨ NAME ✨

• fc_fcp_pkt_destroy — Release hold on a fcp_pkt

🌸 SYNOPSIS 🌸

void fc_fcp_pkt_destroy (struct fc_seq *seq , void *fsp );

🎀 ARGUMENTS 🎀

• seq — The sequence that the FCP packet is on (required by destructor API)
• fsp — The FCP packet to be released

🦋 DESCRIPTION 🦋

This routine is called by a destructor callback in the fc_exch_seq_send routine of the libfc Transport Template. The struct fc_seq is a required argument even though it is not used by this routine.

💜 CONTEXT 💜

No locking required.

🌈 SEE ALSO 🌈

The whole squad, gathered here for your reading pleasure:

• Kernel file ./drivers/scsi/libfc/fc_fcp.c
• struct fc_fcp_internal(9)
• fc_fcp_pkt_alloc(9)
• fc_fcp_pkt_release(9)
• fc_fcp_pkt_hold(9)
• fc_fcp_lock_pkt(9)
• fc_fcp_unlock_pkt(9)
• fc_fcp_timer_set(9)
• fc_fcp_send_abort(9)
• fc_fcp_retry_cmd(9)
• fc_fcp_ddp_setup(9)
• fc_fcp_ddp_done(9)
• fc_fcp_can_queue_ramp_up(9)
• fc_fcp_can_queue_ramp_down(9)
• get_fsp_rec_tov(9)
• fc_fcp_recv_data(9)
• fc_fcp_send_data(9)
• fc_fcp_abts_resp(9)
• fc_fcp_recv(9)
• fc_fcp_resp(9)
• fc_fcp_complete_locked(9)
• fc_fcp_cleanup_cmd(9)
• fc_fcp_cleanup_each_cmd(9)
• fc_fcp_abort_io(9)
• fc_fcp_pkt_send(9)
• fc_fcp_cmd_send(9)
• fc_fcp_error(9)
• fc_fcp_pkt_abort(9)
• fc_lun_reset_send(9)
• fc_lun_reset(9)
• fc_tm_done(9)
• fc_fcp_cleanup(9)
• fc_fcp_timeout(9)
• fc_fcp_rec(9)
• fc_fcp_rec_resp(9)
• fc_fcp_rec_error(9)
• fc_fcp_recovery(9)
• fc_fcp_srr(9)
• fc_fcp_srr_resp(9)
• fc_fcp_srr_error(9)
• fc_fcp_lport_queue_ready(9)
• fc_queuecommand(9)
• fc_io_compl(9)
• fc_eh_abort(9)
• fc_eh_device_reset(9)
• fc_eh_host_reset(9)
• fc_sdev_init(9)
• fc_fcp_destroy(9)
• fc_fcp_init(9)

That's the whole page, bestie 💖 — brought to you by ./drivers/scsi/libfc, dated October 2026, and literally titled fc_fcp_pkt_destroy(9). Slay 🫶✨