lib/hexdump.c

File Facts

System

Linux kernel

Corpus path

lib/hexdump.c

Extension

.c

Size

8700 bytes

Lines

297

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

• Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.

Dependency Surface

• linux/types.h
• linux/ctype.h
• linux/errno.h
• linux/hex.h
• linux/kernel.h
• linux/minmax.h
• linux/export.h
• linux/unaligned.h

Detected Declarations

• function to
• function hex2bin
• function hex_dump_to_buffer
• function print_hex_dump
• export hex_asc
• export hex_asc_upper
• export hex_to_bin
• export hex2bin
• export bin2hex
• export hex_dump_to_buffer
• export print_hex_dump

Annotated Snippet

switch (prefix_type) {
		case DUMP_PREFIX_ADDRESS:
			printk("%s%s%p: %s\n",
			       level, prefix_str, ptr + i, linebuf);
			break;
		case DUMP_PREFIX_OFFSET:
			printk("%s%s%.8x: %s\n", level, prefix_str, i, linebuf);
			break;
		default:
			printk("%s%s%s\n", level, prefix_str, linebuf);
			break;
		}
	}
}
EXPORT_SYMBOL(print_hex_dump);

#endif /* defined(CONFIG_PRINTK) */

Annotation

• Immediate include surface: `linux/types.h`, `linux/ctype.h`, `linux/errno.h`, `linux/hex.h`, `linux/kernel.h`, `linux/minmax.h`, `linux/export.h`, `linux/unaligned.h`.
• Detected declarations: `function to`, `function hex2bin`, `function hex_dump_to_buffer`, `function print_hex_dump`, `export hex_asc`, `export hex_asc_upper`, `export hex_to_bin`, `export hex2bin`, `export bin2hex`, `export hex_dump_to_buffer`.
• Atlas domain: Kernel Services / lib.
• Implementation status: integration 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.