drivers/s390/block/dasd_eer.c

File Facts

System

Linux kernel

Corpus path

drivers/s390/block/dasd_eer.c

Extension

.c

Size

20533 bytes

Lines

720

Domain

Driver Families

Bucket

drivers/s390

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/export.h
• linux/init.h
• linux/fs.h
• linux/kernel.h
• linux/miscdevice.h
• linux/module.h
• linux/moduleparam.h
• linux/device.h
• linux/poll.h
• linux/mutex.h
• linux/err.h
• linux/slab.h
• linux/uaccess.h
• linux/atomic.h
• asm/ebcdic.h
• dasd_int.h
• dasd_eckd.h

Detected Declarations

• struct eerbuffer
• struct dasd_eer_header
• function dasd_eer_get_free_bytes
• function dasd_eer_get_filled_bytes
• function dasd_eer_write_buffer
• function dasd_eer_read_buffer
• function dasd_eer_start_record
• function dasd_eer_free_buffer_pages
• function dasd_eer_allocate_buffer_pages
• function dasd_eer_write_standard_trigger
• function dasd_eer_write_snss_trigger
• function dasd_eer_write
• function dasd_eer_snss
• function dasd_eer_snss_cb
• function dasd_eer_enable
• function dasd_eer_disable
• function dasd_eer_open
• function dasd_eer_close
• function dasd_eer_read
• function dasd_eer_poll
• function dasd_eer_init
• function dasd_eer_exit
• export dasd_eer_write

Annotated Snippet

static const struct file_operations dasd_eer_fops = {
	.open		= &dasd_eer_open,
	.release	= &dasd_eer_close,
	.read		= &dasd_eer_read,
	.poll		= &dasd_eer_poll,
	.owner		= THIS_MODULE,
	.llseek		= noop_llseek,
};

static struct miscdevice *dasd_eer_dev = NULL;

int __init dasd_eer_init(void)
{
	int rc;

	dasd_eer_dev = kzalloc_obj(*dasd_eer_dev);
	if (!dasd_eer_dev)
		return -ENOMEM;

	dasd_eer_dev->minor = MISC_DYNAMIC_MINOR;
	dasd_eer_dev->name  = "dasd_eer";
	dasd_eer_dev->fops  = &dasd_eer_fops;

	rc = misc_register(dasd_eer_dev);
	if (rc) {
		kfree(dasd_eer_dev);
		dasd_eer_dev = NULL;
		DBF_EVENT(DBF_ERR, "%s", "dasd_eer_init could not "
		       "register misc device");
		return rc;
	}

	return 0;
}

void dasd_eer_exit(void)
{
	if (dasd_eer_dev) {
		misc_deregister(dasd_eer_dev);
		kfree(dasd_eer_dev);
		dasd_eer_dev = NULL;
	}
}

Annotation

• Immediate include surface: `linux/export.h`, `linux/init.h`, `linux/fs.h`, `linux/kernel.h`, `linux/miscdevice.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/device.h`.
• Detected declarations: `struct eerbuffer`, `struct dasd_eer_header`, `function dasd_eer_get_free_bytes`, `function dasd_eer_get_filled_bytes`, `function dasd_eer_write_buffer`, `function dasd_eer_read_buffer`, `function dasd_eer_start_record`, `function dasd_eer_free_buffer_pages`, `function dasd_eer_allocate_buffer_pages`, `function dasd_eer_write_standard_trigger`.
• Atlas domain: Driver Families / drivers/s390.
• Implementation status: pattern implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• 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.