linux-kernel - SLES10 SP1 (x86_64): Hard-hang when using NFSv4 from HP-UX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Aug 2008 12:41:14 +0200
From:	"Ulrich Windl" <ulrich.windl@...uni-regensburg.de>
To:	linux-kernel@...r.kernel.org
CC:	Ulrich.windl@...uni-regensburg.de
Subject: SLES10 SP1 (x86_64): Hard-hang when using NFSv4 from HP-UX

Hello,

I'm fighting for a while with using NFSv4 provided by HP-UX 11.31 (ONCplus 
B.11.31.04 (ONC+ 2.3)) on a SLES10 SP1 (x86_64) client. HP's NFS is basically that 
from Sun. The problems are:

Mounting the filesystems as NFSv3 causes no problems at all, using NFSv4 makes 
every file open() attempt to hang hard. I must "kill -9" the processes. Even 
"umount -vat nfs4" hangs on umount().

The only messages I get when trying an open is
kernel: Error: state recovery failed on NFSv4 server 192.168.0.20 with error 5

For umount the error message seems to be
rksapas08 kernel: Error: state recovery failed on NFSv4 server 192.168.0.20 with 
error 2

On the HP-UX server I see messages like these, but I'm unsure whether they are 
related to Linux:
vmunix: NOTICE: sec_clnt_geth: unknown authflavor 2037596260, trying AUTH_NONE
vmunix: NOTICE: sec_clnt_geth: unknown authflavor 10, trying AUTH_NONE

When HP-UX uses NFSv4 (same software as quoted above), no such problems appear. 
The server is a four-core Itanium2 (IA64) machine.

I'd appreciate any help towards understanding the error messages and debugging the 
problem.

Regards,
Ulrich
P.S. Not subscribed, so please CC:

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/