PROBLEM: (72111, 74264) (PATCH ID: OSF445-012) ******** This patch fixes a problem with verify. When verify is run on a brand new domain, nfs warnings are displayed even though no nfs related activity is being done. PROBLEM: (BCGMC0WVV) (PATCH ID: OSF445-040) ******** This patch fixes a system hang that could last up to a few minutes with large files when performing synchronous IO requests. The fix is to split up msync() requests into manageable pieces so users can continue working. PROBLEM: (76777) (PATCH ID: OSF445-068) ******** This patch fixes a problem where the output of a "ps" command, the PAGEIN column reports 0 for all processes. After installing this patch, the ps PAGEIN value increases as advfs accesses the disk for vm accesses (but not for normal file read). PROBLEM: (80270) (PATCH ID: OSF445-073) ******** This patch turns off AdvFS assert which, when turned on, a performance degradation in Advfs occurs. The Advfs assert are used for isolating problems during development. PROBLEM: (79769) (PATCH ID: OSF445-079) ******** A kernel memory fault can occur on an smp machine when one thread is extending a clone frags file and another thread does a stat system call on a file with a frag. The stack trace is as follows: 5 panic src/kernel/bsd/subr_prf.c : 804 6 trap src/kernel/arch/alpha/trap.c : 1762 7 _XentMM src/kernel/arch/alpha/locore.s : 1748 8 x_page_to_blk src/kernel/msfs/bs/bs_stg.c : 6191 9 x_page_to_blkmap src/kernel/msfs/bs/bs_stg.c : 5928 10 x_page_mapped src/kernel/msfs/bs/bs_stg.c : 6281 11 bs_frag_has_stg src/kernel/msfs/bs/bs_bitfile_sets.c : 2229 12 msfs_getattr src/kernel/msfs/osf/msfs_vnops.c : 1525 13 vn_stat src/kernel/vfs/vfs_vnops.c : 1277 14 stat1 src/kernel/vfs/vfs_syscalls.c : 3056 15 lstat src/kernel/vfs/vfs_syscalls.c : 3034 16 syscall src/kernel/arch/alpha/syscall_trap.c : 627 17 _Xsyscall src/kernel/arch/alpha/locore.s : 1512 PROBLEM: (77274, 78605) (PATCH ID: OSF445-083) ******** This patch fixes a problem with AdvFS. An AdvFS domain becomes inaccessible when using the mount -d option. PROBLEM: (BCPMB215Q) (PATCH ID: OSF445-005) ******** This patch fixes a kernel memory fault in VMAC code if_addnewaddr(). The fault will occur from ifconfig(8) and the stack will include: _XentMM bcmp if_addnewaddr ifioctl soo_ioctl ioctl_base ioctl syscall PROBLEM: (UVO74098) (PATCH ID: OSF445-007) ******** This patch adds a fix to VMAC functionality when used with NETrain. PROBLEM: (EVT91336A) (PATCH ID: OSF445-010) ******** This patch fixes a problem where the following can occur during a system panic: - system calls interrupts - mpsleep() returns an EINTR error when the panicstr is non-NULL - an indefinite looping at a very high priority PROBLEM: (MGO85573B, N/A) (PATCH ID: OSF445-016) ******** This patch fixes a bug such that when 'fuser -k' is issued on a dismounted NFS mount point in which some process is running, a hang will occur. A new flag, -p, has been introduced. When the -p flag is used with the -c flag, as in 'fuser -c -p -k /mnt', the parent directories are ignored and the processes are gracefully killed. PROBLEM: (74277, 74545) (PATCH ID: OSF445-017) ******** This patch fixes a problem in which operations on NFS files can hang indefinately. PROBLEM: (13096) (PATCH ID: OSF445-026) ******** In the per-VP scheduling state that is shared between the kernel and the DECthreads library scheduler, the compiler generates ldq/stq pairs for a 32-bit data object that neighbors another 32-bit variable. This patch fixes the stq that causes a word tear that corrupts the per-VP floating point flag field called nxm_fp_owned. The affected data structures are defined in . PROBLEM: (BCGM10RFF, 77112) (PATCH ID: OSF445-004) ******** This patch fixes a problem where if the size of a message queue was increased, writers to the queue that were blocked would not wake up for processing. The msgctl(2) and msgsnd(2) system calls now test if the message queue size has increased and if there are writers waiting to get unblocked, then wakeup the writers and let them proceed. PROBLEM: (HPAQB1FTS) (PATCH ID: OSF445-049) ******** This patch fixes a system panic with panic string: "psig: catch not set" An example stack trace is as follows: panic() psig() mach_checksig() PROBLEM: (QCAPUN003) (PATCH ID: OSF445-062) ******** This patch fixes a problem where the system appears to hang. A child process is holding a lock too long and preventing other processes from doing work. The child process is waiting to be re-parented as its parent is winding down. No new processes can be created, although certain existing processes will still continue to function. A forced crash will reveal several processes waiting for the pgrphash lock. The pgrphash lock will be held by a child process waiting for its parent to die which is being held up by an external event. A sample stack trace for the child process holding the pgrphash lock 0 thread_block 1 get_parent 2 fixjobc 3 pgmv 4 setpgrp1 5 setpgid 6 syscall 7 _Xsyscall PROBLEM: (77713) (PATCH ID: OSF445-064) ******** This patch fixes a problem in which the POSIX interval timer is not resilent to clock slowdown cause either by NTP or by a backwards change of the clock. PROBLEM: (ISO100518) (PATCH ID: OSF445-066) ******** This patch fixes a kernel memory fault panic seen under certain circumstances when a process or thread was setting its priority. A typical stack trace would be: > 0 boot src/kernel/arch/alpha/machdep.c : 1890 1 panic src/kernel/bsd/subr_prf.c : 834 2 trap src/kernel/arch/alpha/trap.c : 1659 3 _XentMM src/kernel/arch/alpha/locore.s : 1645 4 nxm_manager_boost src/kernel/kern/syscall_subr.c : 2503 5 trap src/kernel/arch/alpha/trap.c : 2132 6 _Xsyscall src/kernel/arch/alpha/locore.s : 1537 PROBLEM: (BCSM702LV, MGO59344E, MGO75812A) (PATCH ID: OSF445-101) ******** There is a potential for a system panic in routine sbflush() if there is an attempt to flush a socket buffer while it is locked by another thread. This patch corrects the problem. PROBLEM: (73112, 78765) (PATCH ID: OSF445-095) ******** This patch fixes two panics that has the following error messages: simple_lock: time limit exceeded -and- simple_lock: lock already owned by cpu Sample stack traces are listed below: Stack trace #1 simple_lock: time limit exceeded pc of caller: 0xffffffff000adf44 lock address: 0xfffffc001879ca80 lock info addr: 0xfffffc0001404cd0 lock class name: task.lock current lock state: 0xd00000bd000ac4cd panic (cpu 0): simple_lock: time limit exceeded syncing disks... done Stack trace #2 12 panic("simple_lock: lock already owned by cpu") 13 simple_lock_fault() 14 simple_lock_state_violation() 15 thread_deallocate() 16 task_swapout() 17 task_swapout_thread() PROBLEM: (HPAQ20N23) (PATCH ID: OSF445-069) ******** This patch corrects a problem with the incorrect ordering of network interfaces which was resulting in network partitions. PROBLEM: (HPAQ30SQ8) (PATCH ID: OSF445-008) ******** This patch fixes a panic in in_pcbfree() when ASE fails over NFS applications that use listener sockets. The stack trace will look like the following: panic in_pcbfree tcp_input ipintr netisr_thread PROBLEM: (BCSM412FX) (PATCH ID: OSF445-065) ******** This patch fixes a panic in in_pcbfree() when NFS is implemented over TCP. If an NFS server stops servicing requests to clients and the server is rebooted to clear the NFS problem, the clients panic in in_pcbfree(). A typical client stack trace is: panic in_pcbfree tcp_input ipintr PROBLEM: (EVT19938A, MGO53352A, TKTB30013, 79783, BCSM50XTD, BCSM511NN, BCSM51BGL) (PATCH ID: OSF445-075) ******** This patch fixes problems seen in the relocation of NFS services when clients have at least one of the filesystems mounted over TCP. The symptom is that at least one of the filesystems will fail to unmount when the failover is attempted. When analysis of that system is completed, at least one of the nfs_tcp_threads will be hung in rrok3free(). The stack trace will look similar to this: 0 thread_block() 1 mpsleep() 2 rrok3free() 3 svcktcp_reply() 4 svc_sendreply() 5 rfs_sendreply() 6 rfs_dispatch() 7 nfs_rpc_recv() 8 nfs_tcp_thread () PROBLEM: (MGO45830B) (PATCH ID: OSF445-002) ******** System spends excessive time in the internet checksum routine due to an invalid message length. Performance is degraded significantly. PROBLEM: (67762, 74793, HPAQ112FQ) (PATCH ID: OSF445-058) ******** This patch fixes reply values for NFS writes which were causing protocol violations. PROBLEM: (MGO59344C, 80674) (PATCH ID: OSF445-106) ******** 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. PROBLEM: (TKTBC0035, 78015) (PATCH ID: OSF445-015) ******** This patch fixes a problem where the operating system only looks in slot 0 for the primary CPU when in console mode. This can be seen when examining the binary.errlog with the DECevent utility. On a EV6 CPU system, DECevent displays the text in an incorrect format that translates to an EV5 CPU. PROBLEM: (74651, 75705) (PATCH ID: OSF445-013) ******** This patch fixes a problem where a root user was not allowed to check file access on behalf of a user without completely becoming the user. The functionality is needed by the ASU (Advanced Server for UNIX) product. PROBLEM: (MGO90721A) (PATCH ID: OSF445-029) ******** This patch fixes a problem with simple_lock: time limit exceeded panic seen on SMP systems with the namei.nch_lockinfo lock. A typical entry in the /var/adm/messages file would be: simple_lock: time limit exceeded pc of caller: 0xfffffc00004445d8 lock address: 0xfffffc0000eb50e8 lock info addr: 0xfffffc0000772be0 lock class name: namei.nch_lockinfo current lock state: 0x800000be00443b45 (cpu=0,pc=0xfffffc0000443b44,busy) PROBLEM: (TKTR30001) (PATCH ID: OSF445-037) ******** This patch fixes a race condition in the UBC code where a lookup is done on a page being invalidated (freed). The lookup continued to access the data structure after it was freed, and depending on who uses the data structure next, this causes the lookup to think that the invalidation did not complete and wait. PROBLEM: (58325) (PATCH ID: OSF445-052) ******** This patch fixes UFS metadata update performance by adding a mount option, "delayed", for UFS to convert synchronous metadata writes into delayed metadata writes. The File System is often used as a cache for transitory data such as in web servers. Applications such as Squid web proxy server will get a significant performance boost by enabling this option. Restoring from tape is another application that can be benefited from this. PROBLEM: (79937) (PATCH ID: OSF445-076) ******** This patch fixes a hang or simple_lock_state_violation panic in biodone. This patch places mount throttle fields under the new mount_throttle_lock (locking requirements described in mount.h). These fields previously were under the mount lock. The problem is that it was possible for the mount lock to be held in a context which could be interrupted by a higher priority event, such as biodone, which could also require this lock. The solution is to protect these fields under a different lock and spl. The key pieces of the stack trace for this problem are: biodone() -- wants mount lock ... ... -- interrupt service routines ... _XentInt() -- interrupt ... vfs_unbusy() -- some routine which takes the mount lock (vfs_unbusy is not unique here) ... PROBLEM: (82489, SSRT0676U) (PATCH ID: OSF445-171) ******** 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: (STL069451) (PATCH ID: OSF445-144) ******** This patch corrects a problem in which a single application's creating and removing of files repeatedly in the absence of other applications working on the same fileset can cause poor 'update' daemon performance due to a flawed kernel hashing algorithm. PROBLEM: (BCGM805NL) (PATCH ID: OSF445-189) ******** These changes address panics which can occur if a signal is sent to a multi-threaded task in which one or more threads are calling exit() or exec(). The panic is invariably a kernel memory fault whose faulting virtual address is usually 0x50. The following panic message is typical: trap: invalid memory read access from kernel mode faulting virtual address: 0x0000000000000050 pc of faulting instruction: 0xfffffc0000283bc0 ra contents at time of fault: 0xfffffc0000283bb4 sp contents at time of fault: 0xfffffe0450d77360 An example stack trace: 0 thread_block 1 thread_preempt 2 boot 3 panic 4 trap 5 _XentMM 6 thread_signal_wakeup 7 psignal_internal 8 kill 9 syscall 10 _Xsyscall PROBLEM: (81379, 77978) (PATCH ID: OSF445-131) ******** The system returns the incorrect status from read EEROM. PROBLEM: (76224) (PATCH ID: OSF445-123) ******** This patch corrects a problem where a directory entry may be attempted to be changed to "." and the code checks for this prevents it from happening. PROBLEM: (78711, 78577, 78703, 78751, 79066) (PATCH ID: OSF445-133) ******** This patch fixes a panic in AdvFS which has the following error message: panic: Unaligned kernel space access from kernel mode The stack trace is listed below: 21 afault_trap() 22 _XentUna() 23 seq_search() 24 msfs_lookup() 25 cfs_comm_lookup() 26 cfscall_lookup() 27 cfs_lookup() 29 _F64_stat1() 30 lstat() 31 syscall() 32 _Xsyscall() PROBLEM: (83661, 85312, STL111443) (PATCH ID: OSF445-182) ******** This patch fixes a problem where the setgid bit of a directory was not being set when created, if its parent directory has the setgid bit set. PROBLEM: (MGO69211A) (PATCH ID: OSF445-178) ******** This patch fixes an AdvFS hang that is caused by a thread waiting for flushCv notification and is holding resources that other threads want. This type of hang has been experienced when shutting the system down. PROBLEM: (ALC-2-076) (PATCH ID: OSF445-173) ******** This patch provides support for activating temporary atomic write data logging on all files within the mount point. The data logging is turned off when the fileset is unmounted. PROBLEM: (80302, 80232) (PATCH ID: OSF445-119) ******** This patch fixes a kernel memory fault from ufs_mount(). PROBLEM: (BCPMB0MC4, 117-2-306, 84332) (PATCH ID: OSF445-172) ******** This patch fixes a system hang caused by netisr queue corruption due to a race condition that is primarily encountered by third party drivers and layered products that call schednetisr_nospl(). PROBLEM: (MGO16194A) (PATCH ID: OSF445-196) ******** This patch fixes the simple lock timeout panic seen when working with NFS loopback mounted file systems with large numbers of dirty pages. The stack trace will usualy include ubc_written_cluster(). : 3 panic 4 trap 5 _XentMM 6 ubc_page_alloc 7 nfs3_getapage 8 nfs3_getpage 9 rw3vp_cache 10 rw3vp 11 nfs3_rdwr 12 vn_write 13 rwuio 14 write 15 syscall 16 _Xsyscall PROBLEM: (68328, 68412) (PATCH ID: OSF445-120) ******** This patch prevents a system panic from occurring while using ADVFS. A typical stack trace may look similar to this: 5 panic(s = "SMP Assertion failed") 6 advfs_sad() 7 vd_htop_already_valid() 8 migrate_normal() 9 mig_migrate() 10 bs_migrate() 11 msfs_syscall_op_migrate() 12 msfs_real_syscall() 13 msfs_syscall() 14 syscall() 15 _Xsyscall() PROBLEM: (79241, 79696, 80978) (PATCH ID: OSF445-126) ******** This patch fixes "simple_lock: time limit exceeded" system panic either from cache_lookup() or cache_enter(). This is caused by the namecache LRU list getting corrupted. PROBLEM: (HPAQ30LKL) (PATCH ID: OSF445-151) ******** This patch fixes inaccuracy problems when using setrlimit/getrlimit with a threaded application. PROBLEM: (78704) (PATCH ID: OSF445-191) ******** This patch fixes a hang in the ufs filesystem. PROBLEM: (EVT0523123) (PATCH ID: OSF445-190) ******** This patch fixes a memory leak when named pipes (FIFOs) are used. PROBLEM: (BCPM91FRG, 82491) (PATCH ID: OSF445-188) ******** This patch fixes a problem that causes Tarantella Enterprise 1.41 not to install on Tru64 UNIX. PROBLEM: (84853) (PATCH ID: OSF445-166) ******** CDFS media burned in 2001 shows the wrong dates. PROBLEM: (ALC-2-076) (PATCH ID: OSF445-200) ******** This patch fixes a timing window where flushing data to disk can be incomplete when a system is going down. Note this can only occur if all of these conditions are true: o More than one thread calls the reboot() system call without first going through shutdown, /sbin/reboot, or /sbin/halt (note the operating system itself does not do this, it would have to be an application program which is calling reboot()). o O_SYNC is not in use. o AdvFS data logging is not in use. PROBLEM: (MGO10736A, EVT0396650, TPOB36405, BCSM10NZK) (PATCH ID: OSF445-187) ******** This patch fixes a problem where threads can hang in x_load_inmem_xtnt_map() when called from x_page_to_blkmap(). A typical hung thread will have the following calls at the top of its stack trace: 0 thread_block 1 lock_read 2 x_load_inmem_xtnt_map 3 x_page_to_blkmap 4 x_page_to_iolist 5 blkmap PROBLEM: (ALC-2-076) (PATCH ID: OSF445-197) ******** This patch fixes a potential problem flushing data to disk when using data logging with sparse files in an AdvFS filesystem. PROBLEM: (GB_G00942) (PATCH ID: OSF445-195) ******** This patch corrects an AdvFS panic which can occur during a rmfset operation. The panic string: "rbf_delete_int: can't find bf attributes" PROBLEM: (MGO02694A) (PATCH ID: OSF445-179) ******** This patch fixes hangs in AdvFS fileset operations such as clone creation and deletion when I/O errors or device full conditions resulted in the operation being "undone". PROBLEM: (GOZ96332B) (PATCH ID: OSF445-203) ******** This patch fixes a problem when using multiple subnets on a netowrk interface; ARP request packets sent by the system will contain the IP alias address in the sender field when that alias is in the same subnet as the requested IP address. PROBLEM: (GOZ03925B) (PATCH ID: OSF445-204) ******** This patch fixes a problem when using an IP alias address on a network interface. Applications making IOCTL calls (such as SIOGIFNETMASK and SIOCGIFBRADDR) accessing the IP alias address will now return the correct values for the alias instead of the primary address. PROBLEM: (HGO073056) (PATCH ID: OSF445-186) ******** This patch fixes a problem where threads can hang while renaming files on nfs mounted filesystems. This can occur when two threads are renaming files, one from directory "a" to directory "b" and the other from directory "b" to "a". A typical stack trace for a hung thread looks like: 0 thread_block 1 lock_write 2 nfs3_rename 3 rename 4 syscall PROBLEM: (EVT18628A, 59132) (PATCH ID: OSF445-212) ******** This patch modifies advfs kernel code and several utilities. AdvFS will no longer panic with the following error: ADVFS EXCEPTION : panic cpu(0) : bad frag free list. The code is modified so that during frag allocation when advfs determines that the frag group header's free list has been corrupted, it stops using it and marks it BAD. It is then removed from the free list so no more allocations can take place AND no deallocations are performed. The verify, shfragbf and vfragpg programs are modified to report BAD frag groups. PROBLEM: (76966) (PATCH ID: OSF445-116) ******** This patch fixes two problems with the consvar command: 1. Consvar -s now sets a tape device as a boot device from the console 2. Consvar -g now displays a listing of the console settings as intended PROBLEM: (87559) (PATCH ID: OSF445-242) ******** The problem causes a system panic. The panic string will be: "simple_unlock: lock not owned by cpu" and will occur in the biodone routine. Typical stack trace: (dbx) t > 0 stop_secondary_cpu() 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 simple_lock_fault() 7 simple_unlock_owner_violation() 8 biodone() 9 cdisk_complete() 10 xpt_callback_thread()