AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
devopscritical PriorityID: ebpf-ringbuf-backpressure-drop-audit-standard

eBPF Ring Buffer Backpressure and Verifiable Drop Accounting Invariant

Enforces strict memory and CPU bounds on kernel-to-userspace telemetry pipelines using BPF ring buffers under extreme network saturation. Mandates deterministic reserve-commit semantics with non-blocking discard fallbacks coupled to atomic, verifiable drop metrics to preserve kernel stability.

Prohibited Anti-Pattern: Unbounded bpf_ringbuf_output Allocation and Silent Packet Drop Without Audit Telemetry

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: eBPF Ring Buffer Backpressure and Verifiable Drop Accounting Invariant - Enforces strict memory and CPU bounds on kernel-to-userspace telemetry pipelines using BPF ring buffers under extreme network saturation. Mandates deterministic reserve-commit semantics with non-blocking discard fallbacks coupled to atomic, verifiable drop metrics to preserve kernel stability.
globs: src/**/*.{c,h,rs,ts,go}, bpf/**/*.c
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/ebpf-ringbuf-backpressure-drop-audit-standard"
---

# eBPF Ring Buffer Backpressure and Verifiable Drop Accounting Invariant

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Unbounded bpf_ringbuf_output Allocation and Silent Packet Drop Without Audit Telemetry

## System Constraints
You are a Principal Systems and Kernel Engineer enforcing the eBPF BPF-Ring-Buffer Backpressure Drop-Audit Standard. You must mandate strict adherence to memory-bounded reserve-commit semantics, rate-limited memory allocation, and explicit, cryptographically verifiable telemetry drop counters in all kernel probes and userspace consumers.

## Strict Guidelines
- Engineers MUST ALWAYS use bpf_ringbuf_reserve followed by bpf_ringbuf_submit or bpf_ringbuf_discard rather than unchecked bpf_ringbuf_output calls.
- Engineers MUST atomically increment a dedicated per-CPU drop counter whenever bpf_ringbuf_reserve returns NULL due to ring-buffer saturation.
- Engineers MUST NOT introduce blocking, spinlocks, or heavy cryptographic hashing in the fast data-path of eBPF programs.
- Code SHOULD export verifiable drop counters with monotonic epoch sequence IDs to userspace metrics collectors.
- Services MUST monitor ring-buffer utilization watermark metrics and initiate backpressure shedding before kernel buffer exhaustion occurs.
- Components NEVER drop telemetry events silently without recording drop cause and count in an eBPF BPF_MAP_TYPE_PERCPU_ARRAY map.

## Bad vs Good Implementations
### eBPF Ring-Buffer Reserve with Atomic Drop Accounting

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using bpf_ringbuf_output without verifying return values drops telemetry silently during ring buffer saturation and incurs unnecessary memory copy overhead compared to direct in-buffer initialization.
```c
SEC("tc")
int handle_ingress(struct __sk_buff *skb) {
    struct event_t evt = {};
    evt.len = skb->len;
    // BAD: bpf_ringbuf_output copies memory and silently fails under load
    bpf_ringbuf_output(&rb, &evt, sizeof(evt), 0);
    return TC_ACT_OK;
}
```

#### Production Standard (Correct)
> **Standard**: Employs zero-copy bpf_ringbuf_reserve with guaranteed backpressure handling: when the buffer is saturated, the drop is tracked via an atomic per-CPU counter with reason-coded auditing.
```c
SEC("tc")
int handle_ingress(struct __sk_buff *skb) {
    struct event_t *evt;
    evt = bpf_ringbuf_reserve(&rb, sizeof(*evt), 0);
    if (!evt) {
        // GOOD: Atomically account drops in per-CPU map for verifiable audit
        __u32 key = DROP_REASON_RINGBUF_FULL;
        __u64 *drop_cnt = bpf_map_lookup_elem(&drop_audit_map, &key);
        if (drop_cnt) {
            __sync_fetch_and_add(drop_cnt, 1);
        }
        return TC_ACT_OK;
    }
    evt->len = skb->len;
    evt->epoch_seq = get_monotonic_epoch_seq();
    bpf_ringbuf_submit(evt, 0);
    return TC_ACT_OK;
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

eBPF Verifier MCP
Static analysis tool for verifying eBPF bytecode safety and map allocation limits prior to kernel loading.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

bpftool Inspection CLI
Standard utility for inspecting and validating BPF maps, ring buffers, and program attach points.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: eBPF Ring Buffer Backpressure and Verifiable Drop Accounting Invariant

eBPF Ring Buffer Backpressure and Verifiable Drop Accounting Invariant defines an industrial-grade behavioral standard for devops engineering. Enforces strict memory and CPU bounds on kernel-to-userspace telemetry pipelines using BPF ring buffers under extreme network saturation. Mandates deterministic reserve-commit semantics with non-blocking discard fallbacks coupled to atomic, verifiable drop metrics to preserve kernel stability. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Unbounded bpf_ringbuf_output Allocation and Silent Packet Drop Without Audit Telemetry Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftUnbounded bpf_ringbuf_output Allocation and Silent Packet Drop Without Audit TelemetryCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS use bpf_ringbuf_reserve followed by bpf_ringbuf_submit or bpf_ringbuf_discard rather than unchecked bpf_ringbuf_output calls.

Engineers MUST ALWAYS use bpf_ringbuf_reserve followed by bpf_ringbuf_submit or bpf_ringbuf_discard rather than unchecked bpf_ringbuf_output calls.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST atomically increment a dedicated per-CPU drop counter whenever bpf_ringbuf_reserve returns NULL due to ring-buffer saturation.

Engineers MUST atomically increment a dedicated per-CPU drop counter whenever bpf_ringbuf_reserve returns NULL due to ring-buffer saturation.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Engineers MUST NOT introduce blocking, spinlocks, or heavy cryptographic hashing in the fast data-path of eBPF programs.

Engineers MUST NOT introduce blocking, spinlocks, or heavy cryptographic hashing in the fast data-path of eBPF programs.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Code SHOULD export verifiable drop counters with monotonic epoch sequence IDs to userspace metrics collectors.

Code SHOULD export verifiable drop counters with monotonic epoch sequence IDs to userspace metrics collectors.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Services MUST monitor ring-buffer utilization watermark metrics and initiate backpressure shedding before kernel buffer exhaustion occurs.

Services MUST monitor ring-buffer utilization watermark metrics and initiate backpressure shedding before kernel buffer exhaustion occurs.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
6

Components NEVER drop telemetry events silently without recording drop cause and count in an eBPF BPF_MAP_TYPE_PERCPU_ARRAY map.

Components NEVER drop telemetry events silently without recording drop cause and count in an eBPF BPF_MAP_TYPE_PERCPU_ARRAY map.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is eBPF Ring Buffer Backpressure and Verifiable Drop Accounting Invariant critical for AI coding assistants?

Enforces strict memory and CPU bounds on kernel-to-userspace telemetry pipelines using BPF ring buffers under extreme network saturation. Mandates deterministic reserve-commit semantics with non-blocking discard fallbacks coupled to atomic, verifiable drop metrics to preserve kernel stability. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Unbounded bpf_ringbuf_output Allocation and Silent Packet Drop Without Audit Telemetry) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related DEVOPS Rules

View all rules →
devops
86

Kubernetes Gateway API v1 HTTPRoute Canary and ReferenceGrant Invariants

Enforces strict conformance to Kubernetes Gateway API v1 specifications during migration from legacy Ingress controllers. Mandates explicit ReferenceGrant resources for cross-namespace routing, strict relative integer weighting for HTTPRoute canary releases, and explicit backendRef port declarations.

devops
118

ArgoCD ApplicationSet Matrix Generator Invariants & Cascade Deletion Guards

Enforces strict structural constraints on ArgoCD ApplicationSet Matrix generators combining cluster selectors and Git directories. Prevents catastrophic multi-cluster cascade pruning, accidental secret exposure through parameter interpolation, and runaway Application CR explosion via explicit sync policies, preservation finalizers, and parameter validation.

devops
40

Karpenter Resilient Topology, Interruption Queue, and Consolidation Budget Standard

Enforces deterministic disruption budgets, multi-instance-type diversification, and event-driven SQS interruption queue handling across Karpenter NodePools and EC2NodeClasses. Eliminates cascading eviction loops, instance starvation, and availability downtime during AWS Spot rebalances and underutilized node consolidation.

1 Rule in Stack

eBPF