padlock-cli 0.9.5

Struct memory layout analyzer for C, C++, Rust, and Go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

// padlock-cli/src/commands/bpf.rs
//
// `padlock bpf` — analyse eBPF object files or binaries containing a .BTF section.
//
// This is a thin wrapper around `padlock analyze` that:
//  1. Prints a one-line note explaining that BTF-derived layouts are compiler-accurate.
//  2. Delegates entirely to the existing analyze pipeline.
//
// All filtering, output format, and severity flags work identically.

use std::path::PathBuf;

use crate::commands::analyze::{self, AnalyzeOpts};
use crate::filter::{FailSeverity, FilterArgs};

pub fn run(
    paths: &[PathBuf],
    json: bool,
    sarif: bool,
    fail_on_severity: Option<FailSeverity>,
    filter: &FilterArgs,
) -> anyhow::Result<()> {
    // Only print the note when outputting human-readable text — skip for JSON/SARIF
    // so machine consumers don't have to strip it.
    if !json && !sarif {
        eprintln!(
            "padlock bpf: analysing BTF section — layouts reflect compiled types (compiler-accurate).\n\
             False-sharing findings on BPF map structs are directly actionable: pad to separate\n\
             frequently-updated map values onto distinct cache lines.\n"
        );
    }

    analyze::run(
        paths,
        AnalyzeOpts {
            json,
            sarif,
            markdown: false,
            cache_line_size: None,
            word_size: None,
            fail_on_severity,
            target: None,
        },
        filter,
    )
}