drivers/md/dm-vdo/permassert.c
Source file repositories/reference/linux-study-clean/drivers/md/dm-vdo/permassert.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/md/dm-vdo/permassert.c- Extension
.c- Size
- 567 bytes
- Lines
- 27
- Domain
- Driver Families
- Bucket
- drivers/md
- 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.
Dependency Surface
permassert.herrors.hlogger.h
Detected Declarations
function vdo_assertion_failed
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* Copyright 2023 Red Hat
*/
#include "permassert.h"
#include "errors.h"
#include "logger.h"
int vdo_assertion_failed(const char *expression_string, const char *file_name,
int line_number, const char *format, ...)
{
va_list args;
va_start(args, format);
vdo_log_embedded_message(VDO_LOG_ERR, VDO_LOGGING_MODULE_NAME, "assertion \"",
format, args, "\" (%s) failed at %s:%d",
expression_string, file_name, line_number);
vdo_log_backtrace(VDO_LOG_ERR);
va_end(args);
return UDS_ASSERTION_FAILED;
}
Annotation
- Immediate include surface: `permassert.h`, `errors.h`, `logger.h`.
- Detected declarations: `function vdo_assertion_failed`.
- Atlas domain: Driver Families / drivers/md.
- 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.