Generic block device drivers (virtio-blk, RBD, zram, loop, nbd, ublk, and legacy floppies)
A catch-all directory holding the kernel's general-purpose block device drivers. It mixes very active virtual and network-backed storage (VirtIO disks for VMs, Ceph RBD images, zram compressed RAM disks, loop devices, NBD, the new ublk userspace block framework, and Xen front/back ends) with a handful of legacy bits like PS3, Amiga/Atari/Mac floppies, ATA-over-Ethernet, and Sun LDOM virtual disks.
recommendation
Worth keeping but worth labelling, because the directory as a whole is one of the busiest in the kernel — feature work for ublk and bug fixes for RBD were still landing in 2026, and zram, loop, NBD, and virtio-blk are core to modern cloud, container, and VM deployments. The annotation case is about the few stragglers inside it (PS3, Amiga/Atari/Mac floppies, AoE, sunvdc, z2ram), which are the candidates that could eventually be split out or retired without affecting the active majority.
repository signals
sources
- lore.kernel.org
Recent upstream feature work is still landing in this directory (ublk persistent device links, April 23, 2026).
- lore.kernel.org
Recent upstream bug-fix traffic also touches long-lived production drivers here (rbd null-ptr-deref fix, April 19, 2026).
- docs.kernel.org
zram is current kernel-documented functionality for swap/tmp/cache use, indicating active real-world deployment rather than archival status.
- docs.ceph.com
The kernel RBD driver remains part of current Ceph operations guidance for mapping block images.
- qemu.org
QEMU still recommends VirtIO devices for virtual machines, supporting ongoing deployment relevance of virtio_blk.
codex reasoning notes (technical)
Not a single obsolete hardware family but an umbrella directory mixing active virtual/pseudo block drivers (virtio_blk, ublk, rbd, loop, nbd, zram, Xen back/front) with some clearly legacy platform code (PS3, Amiga/Atari/Mac floppies, AoE, sunvdc, z2ram). Local shell inspection via `rg --files drivers/block` and marker grep showed that mix. Lore evidence was obtained with `mcp__lore_http__.lore_regex` over patch diffs touching `drivers/block/`, which returned fresh 2026 linux-block patches for ublk, rbd, and null_blk; that is strong evidence against directory-level deprecation/removal. Deployment evidence came from `web.search_query` results on docs.kernel.org, docs.ceph.com, and qemu.org. Because the directory as a whole is active and still relevant in VM/cloud/storage deployments, removal is not justified; annotate or split out stale legacy members instead.