drivers/target/target_core_iblock.h

File Facts

System

Linux kernel

Corpus path

drivers/target/target_core_iblock.h

Extension

.h

Size

874 bytes

Lines

42

Domain

Driver Families

Bucket

drivers/target

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/atomic.h
• linux/refcount.h
• linux/blkdev.h
• target/target_core_base.h

Detected Declarations

• struct iblock_req
• struct iblock_dev_plug
• struct iblock_dev

Annotated Snippet

struct iblock_req {
	refcount_t pending;
	atomic_t ib_bio_err_cnt;
} ____cacheline_aligned;

#define IBDF_HAS_UDEV_PATH		0x01

#define IBD_PLUGF_PLUGGED		0x01

struct iblock_dev_plug {
	struct se_dev_plug se_plug;
	struct blk_plug blk_plug;
	unsigned long flags;
};

struct iblock_dev {
	struct se_device dev;
	unsigned char ibd_udev_path[SE_UDEV_PATH_LEN];
	u32	ibd_flags;
	struct bio_set	ibd_bio_set;
	struct block_device *ibd_bd;
	struct file *ibd_bdev_file;
	bool ibd_readonly;
	bool ibd_exclusive;
	struct iblock_dev_plug *ibd_plug;
} ____cacheline_aligned;

#endif /* TARGET_CORE_IBLOCK_H */

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/refcount.h`, `linux/blkdev.h`, `target/target_core_base.h`.
• Detected declarations: `struct iblock_req`, `struct iblock_dev_plug`, `struct iblock_dev`.
• Atlas domain: Driver Families / drivers/target.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.