scripts/test_gdrdrv_HAVE_VM_FLAGS_SET.sh should honour user-defined kernel source location

Open
  • Is something wrong?
#311 2 comments 0 reactions 0 assignees View on GitHub

@efegokdemir is already working on this.

Since Sep 21, 2026.

Assessment

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

Research direction

Start by comparing the KDIR handling in src/gdrdrv/Makefile with the kernel-source lookup in scripts/test_gdrdrv_HAVE_VM_FLAGS_SET.sh. Run the test with a custom KDIR and verify that it uses that location instead of /lib/modules/${kver}/build, while preserving the default behavior when KDIR is not customized.

Written by the indexing model from the issue text.

Description

The Makefile for the kernel driver, src/gdrdrv/Makefile, allows the user to define a custom location for the kernel sources via the KDIR variable. However, the test script scripts/test_gdrdrv_HAVE_VM_FLAGS_SET.sh ignores the setting and requires the kernel sources to be located in /lib/modules/${kver}/build. This is confusing and can lead to inconsistent results.

Dominant language
C
Stars
1.4k
Forks
198
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from NVIDIA/gdrcopy

All issues in NVIDIA/gdrcopy

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.