scripts/gendwarfksyms/examples/kabi_ex.c

File Facts

System

Linux kernel

Corpus path

scripts/gendwarfksyms/examples/kabi_ex.c

Extension

.c

Size

514 bytes

Lines

38

Domain

Support Tooling And Documentation

Bucket

scripts

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• kabi_ex.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
/*
 * kabi_ex.c
 *
 * Copyright (C) 2024 Google LLC
 *
 * Examples for kABI stability features with --stable. See kabi_ex.h
 * for details.
 */

#include "kabi_ex.h"

struct s e0;
enum e e1;

struct ex0a ex0a;
struct ex0b ex0b;
struct ex0c ex0c;

struct ex1a ex1a;
struct ex1b ex1b;
struct ex1c ex1c;

struct ex2a ex2a;
struct ex2b ex2b;
struct ex2c ex2c;

struct ex3a ex3a;
struct ex3b ex3b;
struct ex3c ex3c;

struct ex4a ex4a;

struct ex5a ex5a;
struct ex5b ex5b;

int ex6a;

Annotation

• Immediate include surface: `kabi_ex.h`.
• Atlas domain: Support Tooling And Documentation / scripts.
• 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.