bnx2i_process_iscsi_error(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– bnx2i_process_iscsi_error β€” the Kernel API Manual, bestie edition πŸ’–

okay so you found a (9) page, which means we are in kernel API territory β€” this one lives in the bnx2i manual and it's all about error notifications, so buckle up πŸŽ€


✨ NAME ✨

bnx2i_process_iscsi_error β€” literally the function that processes error notifications on a given connection πŸ’…


✨ SYNOPSIS ✨

void bnx2i_process_iscsi_error (struct bnx2i_hba *hba , struct
iscsi_kcqe *iscsi_err );

no cap, that's the whole signature 🫢


✨ ARGUMENTS ✨

  • hba β€” a pointer to the adapter structure, aka the whole vibe of the hardware instance 🌸
  • iscsi_err β€” a pointer to the iscsi error kcqe, aka the actual tea about what went wrong πŸ“

✨ DESCRIPTION ✨

so what it does πŸ‘‘ β€” it handles iscsi error notifications coming from the FW (that's the firmware, iykyk).

here's the lore: the firmware, during the initial handshake, classifies iscsi protocol violations / TCP rfc violations into either warning or error indications ✨

  • if the indication is of the "Error" type, the driver will initiate session recovery for that connection/session πŸ”₯
  • if it's a "Warning" type indication, the driver will put out a system log message πŸ“ β€” and bestie, listen, there will be only one message for each type for the life of the session. that's on purpose, to avoid un-necessarily overloading the system πŸ’€
not me emphasizing this but fr fr: one message per type, per session lifetime. the driver is being polite to your logs, respect it πŸ™ˆ

✨ SEE ALSO ✨

kernel file ./drivers/scsi/bnx2i/bnx2i_hwi.c β€” and like, the entire girl squad of related pages, all of them, in order, no skipping 🧚:

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_tcp_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) 🌈


and that's the page, bestie πŸ’œ this one came out of the ./drivers/scsi/bnx2i directory, dated October 2026 β€” so when you cite it, cite it with the date, periodt βœ¨πŸŽ€

πŸ“¦ where this page comes from