bnx2i_process_tcp_error(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bnx2i_process_tcp_error β€” NAME ✨

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” this one's about bnx2i_process_tcp_error, and its whole personality is processing error notifications on a given connection. that's it, that's the job. πŸ’–


🌸 SYNOPSIS 🌸

void bnx2i_process_tcp_error (struct bnx2i_hba *hba , struct iscsi_kcqe
*tcp_err );

like, it takes your adapter and a tcp error kcqe, and it returns... nothing. void. no return value, no drama, just vibes and error handling ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • hba β€” adapter structure pointer 🫢. it's the HBA, she's the main character, she holds everything together.
  • tcp_err β€” tcp error kcqe pointer πŸ’€. yes, the error notification itself, hand-delivered, no cap.

πŸ‘‘ DESCRIPTION πŸ‘‘

ok so real talk: this function handles tcp level error notifications from FW πŸ”₯. that's the entire flex. the firmware (FW, iykyk) comes through with a tcp-level oopsie and this bad boy is the one who catches it. she's giving "designated friend who handles the crisis call at 2am" energy, honestly 😭

no extra lore, no secret side quests β€” that's literally the description. periodt. πŸ’…


πŸ’œ SEE ALSO πŸ’œ

everything lives in the kernel file ./drivers/scsi/bnx2i/bnx2i_hwi.c, and the squad of related functions is huge β€” like a full group chat, so let's roll call πŸ“£:

bnx2i_get_cid_num(9), bnx2i_adjust_qp_size(9), bnx2i_get_link_state(9), bnx2i_iscsi_license_error(9), bnx2i_arm_cq_event_coalescing(9), bnx2i_get_rq_buf(9), bnx2i_put_rq_buf(9), bnx2i_ring_sq_dbell(9), bnx2i_ring_dbell_update_sq_params(9), bnx2i_send_iscsi_login(9), bnx2i_send_iscsi_tmf(9), bnx2i_send_iscsi_text(9), bnx2i_send_iscsi_scsicmd(9), bnx2i_send_iscsi_nopout(9), bnx2i_send_iscsi_logout(9), bnx2i_update_iscsi_conn(9), bnx2i_ep_ofld_timer(9), bnx2i_send_cmd_cleanup_req(9), bnx2i_send_conn_destroy(9), bnx2i_570x_send_conn_ofld_req(9), bnx2i_5771x_send_conn_ofld_req(9), bnx2i_send_conn_ofld_req(9), setup_qp_page_tables(9), bnx2i_alloc_qp_resc(9), bnx2i_free_qp_resc(9), bnx2i_send_fw_iscsi_init_msg(9), bnx2i_process_scsi_cmd_resp(9), bnx2i_process_login_resp(9), bnx2i_process_text_resp(9), bnx2i_process_tmf_resp(9), bnx2i_process_logout_resp(9), bnx2i_process_nopin_local_cmpl(9), bnx2i_unsol_pdu_adjust_rq(9), bnx2i_process_nopin_mesg(9), bnx2i_process_async_mesg(9), bnx2i_process_reject_mesg(9), bnx2i_process_cmd_cleanup_resp(9), bnx2i_percpu_io_thread(9), bnx2i_queue_scsi_cmd_resp(9), bnx2i_process_new_cqes(9), bnx2i_fastpath_notification(9), bnx2i_process_update_conn_cmpl(9), bnx2i_recovery_que_add_conn(9), bnx2i_process_iscsi_error(9), bnx2i_process_conn_destroy_cmpl(9), bnx2i_process_ofld_cmpl(9), bnx2i_indicate_kcqe(9), bnx2i_indicate_netevent(9), bnx2i_cm_connect_cmpl(9), bnx2i_cm_close_cmpl(9), bnx2i_cm_abort_cmpl(9), bnx2i_cm_remote_close(9), bnx2i_cm_remote_abort(9), bnx2i_map_ep_dbell_regs(9)

like... that's the whole extended fam right there 🧚 and yeah, you're gonna want to read up on them if you're digging around in this driver. no skipping, bestie, the list is long for a reason πŸ™ˆ


and that's the page! 🌈 this little gem comes from ./drivers/scsi/bnx2i and it's dated October 2026 πŸ“ β€” so go forth, handle those tcp errors, and slay πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from