PROBLEM: (GOZ100546, GOZ100949, QAR 51038, QAR 64034) (Patch ID: OSF440-063) ******** This patch fixes a problem where NFS does not update mtime and atime for special files and named pipes. PROBLEM: (BCPM9124T) (Patch ID: OSF440-063) ******** This patch fixes a problem that can cause an NFS client application to hang, or causes a "lock already owned by thread" panic when lockmode=4. The problem occurs when the application tries to rename a sub-directory to its parent. A stack trace of a hung NFS client application, or the panicing process, may look like: 0 thread_block() 1 lock_write() 0 thread_block() 1 lock_write() 2 nfs3_rename() 3 rename() 4 syscall() 5 _Xsyscall() PROBLEM: (QAR 66747) (Patch ID: OSF440-063) ******** A potential security vulnerability has been discovered, where under certain circumstances system integrity may be compromised. This may be in the form of improper file or privilege management. Compaq has corrected this potential vulnerability. PROBLEM: (CLD HPAQ200SX, MCPM415SF, HPAQ914NT QAR 45528) (Patch ID: OSF440-063) ******** This patch corrects an NFS client problem where a KMF panic can result from incorrect locking. A typical stack trace would be: 0 boot() ["../../../../src/kernel/arch/alpha/machdep.c":1889 1 panic(s = 0xfffffc00005fcf68 = "kernel memory fault") 2 trap 3 _XentMM 4 atomic_decl 5 clntktcp_freesock 6 clfree 7 rfscall 8 rfs3call 9 nfs3_getattr_otw 10 nfs3getattr 11 nfs3_getattr . . PROBLEM: (CLD BCGM40VQ6, MGO104026, QAR 51061) (Patch ID: OSF440-063) ******** This patch fixes a problem where an NFS client process may hang in the uninterruptable state. Specifically, compilation builds may hang during the ld phase (linking). PROBLEM: (QAR 70269, 70640) (Patch ID: OSF440-075) ******** This patch fixes a restart detection problem with the proplistd daemon. Prior to this fix, when mounting a relocated ASE NFS service with property lists, clients did not detect that the proplistd RPC port number had changed. Clients continued to use the proplistd RPC port number of the old ASE cluster member. PROBLEM: (MGO59344C, 80674) (PATCH ID: OSF440-476) ******** This patch is to prevent a hang that can occur using NFS over TCP. Many NFS TCP server threads will be blocked for several minutes and their stack trace will look like the following: 0 thread_block 1 mpsleep 2 sosleep 3 sosbwait 4 sosend 5 xdrrecmbuf_send 6 svcktcp_reply 7 svc_sendreply 8 rfs_sendreply 9 rfs_dispatch 10 nfs_rpc_recv 11 nfs_tcp_thread This problem is a race condition and will only be seen on SMP systems.