We've discovered a bug in the NFSv4, SL4.4, 2.6.9-42.0.10. We have an extremely simple piece of FORTRAN

        program main
        integer a,b,c
        read(5,*) a,b,c
        stop
        end

If the input matches the data type, all is ok. If, instead of a number, you input a character for any of the 3 variables, the code as compiled by the Intel compiler will crash performing a traceback. If the current directory where the traceback is triggered is an NFSv4 mounted directory, the kernel panics. /var/log/messages posts an NFSv4 race condition before the kernel OOP's.

If you do the same in a non-NFSv4 mounted directory, everything is fine.
IF you do the same in a NFSv3 mounted directory, everything is also fine.

Any suggestions?  How does one go about reporting this?

Reply via email to