NVIDIA / NVIDIA/open-gpu-kernel-modules

pahole.sh lacks executable permission in source archive

Open Beginner friendly
#1,155 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

build-problem
Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

NVIDIA Open GPU Kernel Modules Version

595.71.05

Operating System and Version

6.12.88+deb13-amd64

Kernel Release

6.12.88-1 (2026-05-15) x86_64 GNU/Linux

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
  • I am running on a stable kernel release.
Build Command

sudo dkms build nvidia/595.71.05 -k 6.12.88+deb13-amd64

Terminal output/Build Log

/bin/sh: 1: /var/lib/dkms/nvidia/595.71.05/build/pahole.sh: Permission denied make[4]: *** [.../Makefile.modfinal:64: .../nvidia-drm.ko] Error 126

More Info

Steps to Reproduce:

  1. Extract source archive from nvidia-open-dkms package or clone repository
  2. Run dkms build nvidia/595.71.05 -k 6.12.88+deb13-amd64
  3. Build fails with permission error

Root Cause:
The pahole.sh file is extracted without executable permissions (-rw-r--r-- instead of -rwxr-xr-x). Since DKMS extracts sources fresh for each kernel build, chmod +x is lost on every rebuild.

Expected Behavior:
The pahole.sh file should have executable permissions in the source archive.

Workaround:
Manually run: find /var/lib/dkms/nvidia/*/source/pahole.sh -exec chmod +x {} \;

Proposed Fix:
Add executable permission to pahole.sh in the build system or packaging configuration.

Additional Context:
This affects all DKMS builds of nvidia-open on systems with kernels requiring BTF generation.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating pahole.sh and the build-system or packaging configuration that creates the source archive. Reproduce the DKMS build command, then verify that extracted pahole.sh has executable permissions and the build no longer fails with permission error 126.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.