Skip to content

Estimate Cmd Graph Completeness with Strace #95

@augelu-tng

Description

@augelu-tng

Using strace during a Linux kernel build provides an upper bound on the number of source files accessed.
The table below compares the number of files tracked by the cmd graph with the results from strace:

Config Cmd graph Strace source files Filtered strace source files Remaining unexplained files
linux.v6.17.tinyconfig.x86.tar.gz 2214 4372 2242 28 strace_only.txt, 0 sbom_used_files_only.txt
linux.v6.17.y.gregkh-linux-stable.x86 44683 48955 44911 255 strace_only.txt, 27 sbom_used_files_only.txt

Notes:

  • Strace source files: All files in the source tree that were attempted to open during the build.
  • Filtered strace source files: Subset of strace files excluding Makefile*, Kbuild*, Kconfig*, tools/*, and scripts/*.
  • Remaining unexplained files: Files found by strace but not included in the cmd graph (strace_only.txt) and files found by the cmd graph not included in the strace logs (sbom_used_files_only.txt). These files are likely bugs in the main script that need to be fixed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions