Digiport rebuild RPM on Red Hat Enterprise Linux 8.10 (Ootpa) 'struct task_struct' has no member named 'state'

Realport
1

Virtualization: vmware
Operating System: Red Hat Enterprise Linux 8.10 (Ootpa)
CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos
Kernel: Linux 4.18.0-553.51.1.el8_10.x86_64
Architecture: x86-64

When we are rebuilding the RPM from source RPM we get the error

make[2]: Entering directory ‘/usr/src/kernels/4.18.0-553.51.1.el8_10.x86_64’
CC [M] /root/rpmbuild/BUILD/dgrp-1.9/driver/build/dgrp_common.o
/root/rpmbuild/BUILD/dgrp-1.9/driver/build/dgrp_common.c: In function ‘dgrp_sleep’:
/root/rpmbuild/BUILD/dgrp-1.9/driver/build/dgrp_common.c:197:11: error: ‘struct task_struct’ has no member named ‘state’; did you mean ‘__state’?
current->state = TASK_INTERRUPTIBLE;
^~~~~
__state
/root/rpmbuild/BUILD/dgrp-1.9/driver/build/dgrp_common.c:199:11: error: ‘struct task_struct’ has no member named ‘state’; did you mean ‘__state’?
current->state = TASK_RUNNING;
^~~~~
__state
make[3]: *** [scripts/Makefile.build:318: /root/rpmbuild/BUILD/dgrp-1.9/driver/build/dgrp_common.o] Error 1
make[2]: *** [Makefile:1619: module/root/rpmbuild/BUILD/dgrp-1.9/driver/build] Error 2
make[2]: Leaving directory ‘/usr/src/kernels/4.18.0-553.51.1.el8_10.x86_64’
make[1]: *** [Makefile:68: build] Error 2
make[1]: Leaving directory ‘/root/rpmbuild/BUILD/dgrp-1.9/driver/2.6.27’
make: *** [Makefile:59: build] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.wDaAzI (%build)

as far as I am aware, the state was not changed to __state until kernel 5

I am unsure why this is happening on this particular machine when the same process on another VM works.

Any suggestions ?

2

Your 4.18 kernel would normally work, but RHEL may have backported some of the kernel changes, which can cause issues. We try detecting the RHEL version which is running, but it may not be working in this case.

The topic of a Linux driver install can get quite involved, so I’d recommend using the command # script before starting your install (so that all the output is captured), then provide us the “typescript” file found at the path you ran “script” from (along with your product Serial Number) when you create a support case with us.

3

I eventually was able to track this down to an older file on the problem system.

Working System

  • /usr/bin/gzip -dc /root/rpmbuild/SOURCES/dgrp-1.9.tgz
  • /usr/bin/tar -xvvof -
    drwxrwxr-x paul/paul 0 2024-12-18 02:16 dgrp-1.9/
    Issue system
  • /usr/bin/gzip -dc /root/rpmbuild/SOURCES/dgrp-1.9.tgz
  • /usr/bin/tar -xvvof -
    drwxr-xr-x root/root 0 2020-01-29 02:31 dgrp-1.9/

Found this yesterday.

Replacing the older file with the file from ftp site corrected the issue.

1 Like