Bug#1033288: Build Problems with nvidia-fs-dkms on kernel version 6.1.20

Jannick Loch loch-jannick at t-online.de
Tue Mar 21 15:38:11 GMT 2023


Package: nvidia-fs-dkms
Version: 2.13.5~11.8.0-2

Durimng my update routine, i notice that i have problems with building the nvidia-fs module on the newest linux kernel package
6.1.20. Dkms said that there was an BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. If i remove this directive by comment it out,
i get following error log in make.log:
DKMS make.log for nvidia-fs-2.13 for kernel 6.1.0-7-amd64 (x86_64)
Di 21. Mär 16:37:07 CET 2023
./configure 6.1.0-7-amd64
Picking NVIDIA driver sources from NVIDIA_SRC_DIR=/usr/src/nvidia-current-525.89.02/nvidia-peermem. If that does not meet your expectation, you might have a stale driver still around and that might cause problems.
chmod +x ./create_nv.symvers.sh
./create_nv.symvers.sh 6.1.0-7-amd64
Getting symbol versions from /lib/modules/6.1.0-7-amd64/updates/dkms/nvidia-current.ko ...
Created: /var/lib/dkms/nvidia-fs/2.13/build/nv.symvers
cat nv.symvers >> Module.symvers
checking if uaccess.h access_ok has 3 parameters... no
checking if uaccess.h access_ok has 2 parameters... yes
Checking if blkdev.h has blk_rq_payload_bytes... yes
Checking if fs.h has call_read_iter and call_write_iter... yes
Checking if fs.h has filemap_range_has_page... no
Checking if kiocb structue has ki_complete field... yes
Checking if vm_fault_t exist in mm_types.h... yes
Checking if IOCB_HIPRI flag exists in fs.h... yes
Checking if enum PCIE_SPEED_32_0GT exists in pci.h... yes
Checking if atomic64_t counter is of type long... no
Checking if RQF_COPY_USER is present or not... no
Checking if dma_drain_size and dma_drain_needed are present in struct request_queue... no
Checking if struct proc_ops is present or not ... yes
Checking if split is present in vm_operations_struct or not ... no
Checking if mremap in vm_operations_struct has one parameter... yes
Checking if mremap in vm_operations_struct has two parameters... no
Checking if symbol module_mutex is present... no
Checking if blk-integrity.h is present... yes
KCPPFLAGS="-DCONFIG_NVFS_STATS=y -DGDS_VERSION=1.4.0.29 -DNVFS_ENABLE_KERN_RDMA_SUPPORT -DNVFS_BATCH_SUPPORT=y" CONFIG_NVFS_BATCH_SUPPORT=y CONFIG_NVFS_STATS=y make -j4 -C /lib/modules/6.1.0-7-amd64/build  M=$PWD modules
make[1]: warning: -j4 forced in submake: resetting jobserver mode.
make[1]: Verzeichnis „/usr/src/linux-headers-6.1.0-7-amd64“ wird betreten
   CC [M]  /var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.o
   CC [M]  /var/lib/dkms/nvidia-fs/2.13/build/nvfs-dma.o
   CC [M]  /var/lib/dkms/nvidia-fs/2.13/build/nvfs-mmap.o
   CC [M]  /var/lib/dkms/nvidia-fs/2.13/build/nvfs-pci.o
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.c:853:5: error: conflicting types for ‘rw_verify_area’; have ‘int(int,  struct file *, char *, const loff_t *, size_t)’ {aka ‘int(int,  struct file *, char *, const long long int *, long unsigned int)’}
   853 | int rw_verify_area(int read_write, struct file *file,
       |     ^~~~~~~~~~~~~~
In file included from /usr/src/linux-headers-6.1.0-7-common/include/linux/huge_mm.h:8,
                  from /usr/src/linux-headers-6.1.0-7-common/include/linux/mm.h:743,
                  from /var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.c:34:
/usr/src/linux-headers-6.1.0-7-common/include/linux/fs.h:3200:5: note: previous declaration of ‘rw_verify_area’ with type ‘int(int,  struct file *, const loff_t *, size_t)’ {aka ‘int(int,  struct file *, const long long int *, long unsigned int)’}
  3200 | int rw_verify_area(int, struct file *, const loff_t *, size_t);
       |     ^~~~~~~~~~~~~~
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.c: In function ‘nvfs_direct_io’:
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.c:932:44: error: assignment to ‘void (*)(struct kiocb *, long int)’ from incompatible pointer type ‘void (*)(struct kiocb *, long int,  long int)’ [-Werror=incompatible-pointer-types]
   932 |                 nvfsio->common.ki_complete = nvfs_io_complete;
       |                                            ^
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-mmap.c: In function ‘nvfs_mgroup_mmap_internal’:
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-mmap.c:618:67: error: implicit declaration of function ‘prandom_u32’; did you mean ‘prandom_u32_max’? [-Werror=implicit-function-declaration]
   618 |                 base_index = NVFS_MIN_BASE_INDEX + (unsigned long)prandom_u32();
       |                                                                   ^~~~~~~~~~~
       |                                                                   prandom_u32_max
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.1.0-7-common/scripts/Makefile.build:255: /var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.o] Fehler 1
make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet....
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.1.0-7-common/scripts/Makefile.build:255: /var/lib/dkms/nvidia-fs/2.13/build/nvfs-mmap.o] Fehler 1
make[1]: *** [/usr/src/linux-headers-6.1.0-7-common/Makefile:2037: /var/lib/dkms/nvidia-fs/2.13/build] Fehler 2
make[1]: Verzeichnis „/usr/src/linux-headers-6.1.0-7-amd64“ wird verlassen
make: *** [Makefile:107: module] Fehler 2





I am using Debian GNU/Linux SID with X11 and the Kernel Package 6.1.0-7.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/attachments/20230321/8aa58495/attachment.htm>


More information about the pkg-nvidia-devel mailing list