include/scsi/scsi_eh.h

File Facts

System

Linux kernel

Corpus path

include/scsi/scsi_eh.h

Extension

.h

Size

1769 bytes

Lines

60

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/scatterlist.h
• scsi/scsi_cmnd.h
• scsi/scsi_common.h

Detected Declarations

• struct scsi_device
• struct Scsi_Host
• struct scsi_eh_save
• function scsi_sense_is_deferred

Annotated Snippet

struct scsi_eh_save {
	/* saved state */
	int result;
	unsigned int resid_len;
	int eh_eflags;
	enum dma_data_direction data_direction;
	unsigned underflow;
	unsigned char cmd_len;
	unsigned char prot_op;
	unsigned char cmnd[32];
	struct scsi_data_buffer sdb;
	struct scatterlist sense_sgl;

	/* struct request fields */
#ifdef CONFIG_BLK_INLINE_ENCRYPTION
	struct bio_crypt_ctx *rq_crypt_ctx;
	struct blk_crypto_keyslot *rq_crypt_keyslot;
#endif
};

extern void scsi_eh_prep_cmnd(struct scsi_cmnd *scmd,
		struct scsi_eh_save *ses, unsigned char *cmnd,
		int cmnd_size, unsigned sense_bytes);

extern void scsi_eh_restore_cmnd(struct scsi_cmnd* scmd,
		struct scsi_eh_save *ses);

#endif /* _SCSI_SCSI_EH_H */

Annotation

• Immediate include surface: `linux/scatterlist.h`, `scsi/scsi_cmnd.h`, `scsi/scsi_common.h`.
• Detected declarations: `struct scsi_device`, `struct Scsi_Host`, `struct scsi_eh_save`, `function scsi_sense_is_deferred`.
• Atlas domain: Repository Root And Misc / include.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.