lpfc_els_rcv_rrq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… lpfc_els_rcv_rrq(9) πŸ’…

okay bestie, welcome to the Kernel API Manual page for lpfc_els_rcv_rrq(9) β€” yes, we're doing ELS unsolicited-event business, and yes, it's giving kernel-core but make it cute. πŸ¦‹


✨ NAME ✨

lpfc_els_rcv_rrq β€” process an unsolicited rrq iocb. πŸ’–

🌸 SYNOPSIS 🌸

void lpfc_els_rcv_rrq (struct lpfc_vport *vport , struct lpfc_iocbq
*cmdiocb , struct lpfc_nodelist *ndlp );

πŸŽ€ ARGUMENTS πŸŽ€

  • vport β€” pointer to a host virtual N_Port data structure. 🫢
  • cmdiocb β€” pointer to lpfc command iocb data structure. ✨
  • ndlp β€” pointer to a node-list data structure. 🌸

πŸ¦‹ DESCRIPTION πŸ¦‹

So this routine processes a Reinstate Recovery Qualifier (RRQ) IOCB that shows up as an ELS unsolicited event. Main character energy, honestly.

The acceptance rule is a whole vibe check: a request to RRQ shall only be accepted if the Originator Nx_Port N_Port_ID or the Responder Nx_Port N_Port_ID of the target Exchange is the same as the N_Port_ID of the Nx_Port that makes the request.

If the RRQ is not accepted, an LS_RJT with reason code "Unable to perform command request" and reason code explanation "Invalid Originator S_ID" shall be returned. For now, though, we just unconditionally accept RRQ from the target. periodt. πŸ’…

🌈 SEE ALSO 🌈

okay these are the linked besties, exact names and all β€” no skipping, no cap:


bestie, that's the whole page. source/version: ./drivers/scsi/lpfc, date: October 2026, and the manual is lpfc_els_rcv_rrq(9) β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from