ENUM SCI_IO_STATUS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this is enum sci_io_status(9) from the Kernel API Manual ✨ and it’s the enum that holds all the possible IO completion status values. The way that every value in this enumeration maps directly 1:1 to a value in the enum sci_status enumeration is lowkey iconic β€” so if you want the detailed comments about what a status actually represents, please refer to that enumeration. Periodt πŸ’…

✨ SYNOPSIS ✨

enum sci_io_status {
    SCI_IO_SUCCESS ,
    SCI_IO_FAILURE ,
    SCI_IO_SUCCESS_COMPLETE_BEFORE_START ,
    SCI_IO_SUCCESS_IO_DONE_EARLY ,
    SCI_IO_FAILURE_INVALID_STATE ,
    SCI_IO_FAILURE_INSUFFICIENT_RESOURCES ,
    SCI_IO_FAILURE_UNSUPPORTED_PROTOCOL ,
    SCI_IO_FAILURE_RESPONSE_VALID ,
    SCI_IO_FAILURE_CONTROLLER_SPECIFIC_ERR ,
    SCI_IO_FAILURE_TERMINATED ,
    SCI_IO_FAILURE_REQUIRES_SCSI_ABORT ,
    SCI_IO_FAILURE_INVALID_PARAMETER_VALUE ,
    SCI_IO_FAILURE_NO_NCQ_TAG_AVAILABLE ,
    SCI_IO_FAILURE_PROTOCOL_VIOLATION ,
    SCI_IO_FAILURE_REMOTE_DEVICE_RESET_REQUIRED ,
    SCI_IO_FAILURE_RETRY_REQUIRED ,
    SCI_IO_FAILURE_RETRY_LIMIT_REACHED ,
    SCI_IO_FAILURE_INVALID_REMOTE_DEVICE

};

πŸŽ€ Constants πŸŽ€

vibe check: every single constant below is listed in the source as -- undescribed -- 😭 no cap, that’s genuinely all it says. Slay transparency.

  • SCI_IO_SUCCESS β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE β€” -- undescribed -- 🫠
  • SCI_IO_SUCCESS_COMPLETE_BEFORE_START β€” -- undescribed -- 🫠
  • SCI_IO_SUCCESS_IO_DONE_EARLY β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_INVALID_STATE β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_INSUFFICIENT_RESOURCES β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_UNSUPPORTED_PROTOCOL β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_RESPONSE_VALID β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_CONTROLLER_SPECIFIC_ERR β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_TERMINATED β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_REQUIRES_SCSI_ABORT β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_INVALID_PARAMETER_VALUE β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_NO_NCQ_TAG_AVAILABLE β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_PROTOCOL_VIOLATION β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_REMOTE_DEVICE_RESET_REQUIRED β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_RETRY_REQUIRED β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_RETRY_LIMIT_REACHED β€” -- undescribed -- 🫠
  • SCI_IO_FAILURE_INVALID_REMOTE_DEVICE β€” -- undescribed -- 🫠

🌸 Description 🌸

The Description section is giving β€œadd this API” todo-note energy, ngl: it says to add the API that retrieves the SCU status from the core 🫑 Then it says to check that the following status are properly handled β€” and yes, both items are coming at you exactly:

  • SCI_IO_FAILURE_UNSUPPORTED_PROTOCOL
  • SCI_IO_FAILURE_INVALID_IO_TAG

πŸ”₯ SEE ALSO πŸ”₯

  • Kernel file ./drivers/scsi/isci/isci.h; enum sci_status(9), enum sci_task_status(9), sci_swab32_cpy(9) β€” the whole reference squad, fr fr 🫢 iykyk

cute sign-off: this page came from the source/version ./drivers/scsi/isci, dated October 2026, and its title is enum sci_io_status(9) πŸ’– May your IO completions be SCI_IO_SUCCESS and your vibes be immaculate 🌈✨

πŸ“¦ where this page comes from