LIO iSCSI Target Server
The kernel-side server half of iSCSI: it lets a Linux machine export local block devices, files, or other backstores to remote initiators over TCP/IP as if they were SCSI disks. It is the engine behind targetcli-configured SAN appliances and is widely used in enterprise storage, virtualization hosts, and DIY storage servers.
recommendation
It should stay in the kernel because LIO is the standard in-kernel iSCSI target implementation that turns a Linux box into a SAN server, and it remains the supported way to host iSCSI storage on Red Hat Enterprise Linux 8 and 10 via targetcli. Recent bug fixes in 2026 on linux-scsi, including a use-after-free fix and a CDB validation hardening patch, show it is actively maintained with no replacement on the horizon.
repository signals
sources
- lore.kernel.org
linux-scsi carried an April 15, 2026 functional fix for drivers/target/iscsi ('reject invalid size Extended CDB AHS'), indicating active upstream maintenance.
- lore.kernel.org
linux-scsi carried a January 12, 2026 bug fix for a use-after-free in the iSCSI target path, showing current bug-fix traffic rather than abandonment.
- docs.redhat.com
RHEL 10 documentation still instructs administrators to install targetcli, start the target service, and configure LIO-backed iSCSI targets, showing present-day supported deployment.
- docs.redhat.com
RHEL 8 documents current LIO backstores and iSCSI target configuration, reinforcing that this remains a supported storage-server feature rather than dead legacy code.
codex reasoning notes (technical)
Obtained two lore URLs via mcp__lore_http__.lore_regex on patch diffs matching '^diff --git a/drivers/target/iscsi/' in linux-scsi over the last 5 years; both are recent functional fixes. Obtained the Red Hat docs URLs via web search restricted to official docs. This directory implements the software LIO iSCSI target fabric, not a discrete hardware chipset driver, so hardware lifecycle fields are inherently N/A-like; iSCSI target deployments still exist in enterprise/storage niches, and there is no upstream replacement driver covering the same in-kernel target role.