In a NFS mounted directory against the NFS
sever running kernel 2.4.9-6:
# gcc test.c
Opening 'testlock' for writing.
Trying to get a read lock for 'testlock'
It fails to get a read lock from the NFS
server running 2.4.9-6.
Created attachment 34561 [details]
Red Hat should run the Connectathon testsuite
before making any new kernels. I can provide
the patched source.
It looks like both NFS server and client in
kernel 2.4.9-6 failed the Connectathon testsuite.
I am enclosing it here.
Created attachment 34562 [details]
The Connectathon Testsuite
We have the same problem here on all our nfs servers. This brakes our
This will probably affect 7.2 as well - I think the kernels are relatively the same.
I have been able to verify this with a client/server setup running 2.4.9-6smp on
two minimal 7.2 systems.
The client appears to be hanging in the first fcntl64 syscall generated by the
fcntl library call. Strace shows that this syscall never returns.
Attached are relevant trace files including kernel tracebacks for lockd and the
test program on the client, nlm_debug output on the client, kernel traceback of
lockd on the server, and nlm_debug out on the server.
Created attachment 34583 [details]
Client lockd kernel traceback
NFS file locking is broken. I am working on it now.
It may take me a few days to fix it.
Created attachment 34584 [details]
nlm_debug output of client lockd
Created attachment 34585 [details]
server lockd kernel traceback
Created attachment 34586 [details]
server lockd nlm_debug output
*** Bug 54891 has been marked as a duplicate of this bug. ***
Created attachment 34621 [details]
I posted a patch which seems to work for me.
We have applied the patch to make a custom kernel, and it appears to work
for us also.
I built some new rpms of the 2.4.9-6 and 2.4.9-7(for 7.2) kernels that include
I can put them some place public if its helpful to anyone
I'll put up a kernel with the proposed patch up for testing soon; I'm just
trying to see if it's remotely seen (eg it boots etc)
Please try the kernel at
to see if it indeed works
This will also need to be fixed on the alpha 2.4.9 kernel on 7.1
will the same patch work?
I got 2 little questions :
1/ Has enigma kernel the same problem ? If yes, will the 2.4.9-7.4 work on enigma ?
2/ May we have the kernel-header and kernel-source i386.rpm please ?
I had a look at the 7.2 kernel and found out that the svc code is correct,
however, the nfs patch from redhat undoes this. I removed the these lines
from the nfs patch and rebuild the rpms. The kernel now works fine under both
7.1 and 7.2.
This is fixed in yesterdays kernel erratum.
Thanks for reporting this!