3    Summary of Base Operating System Patches

Patch 59.00

OSF375-059

Patch: fddi_config Fails Attempt To Config The fta Device

State: Existing

The fddi_config program was not shipped with the V3.2G kit. Unfortunately, the fddi_config from previous versions fails when attempting to config the fta device. Applying this file solves the problem.

Patch 67.00

OSF375-370040

Patch: NCR psiop Driver Correction

State: Existing

This patch fixes a problem that occurs with the NCR 53C8XX driver (psiop) which the device may not appear to be on the SCSI bus.

Patch 92.00

OSF375-350216

Patch: volrecover -b Command Correction

State: Existing

This patch fixes a problem that occurs when the -b option of the volrecover command is used. The problem is that a background job spawned to perform the recovery operation fails when a SIGHUP signal is received.

Patch 94.00

OSF375-350221

Patch: mfa Driver Correction

State: Existing

This patch fixes a halt/restart problem with the mfa driver ESP self-test.

Patch 97.00

OSF375-350231

Patch: System V getdirentries() System Call Error

State: Existing

The System V getdirentries() system call did not correctly calculate the number of entries in a directory inode when accessing the /dev/fd file system.

Patch 102.00

OSF375-350237

Patch: find Command Correction

State: Existing

The find command will not handle more than 100 arguments.

Patch 103.00

OSF375-350238

Patch: Mail Sent Using uucp or Output Using uux Error

State: Existing

Mail sent using uucp, or output to Mail from the uux command causes the mail message to be sent from the daemon to root with the following error message: "remote access to path/file denied". The error message is sent to root in a mail message.

Patch 105.00

OSF375-350240

Patch: showmount -e Command Correction

State: Existing

Add the time out options -t nnn & -T to the 'showmount' command.

Patch 106.00

OSF375-350241

Patch: Incorrect Profiling Data

State: Existing

This patch corrects the following:

• Fixes a problem that occurs on a multiprocessor system in which the pfm driver does not provide any profiling data on CPUs other than #0.

• Fixes a problem that occurs on systems with recent CPU hardware (EV5) in which using the kprofile command will cause the system to hang.

Patch 111.01

OSF375-350249-1

Patch: Kernel LMF Corrections

State: Existing

Permits kernel components to release license units that have been allocated through lmf_auth_ex().

Patch 112.00

OSF375-350251

Patch: Kernel Memory Fault Panic (bcopy) Correction

State: Existing

System panics with a kernel memory fault in k_mem_fault.

Patch 118.00

OSF375-350263

Patch: Mail From "daemon" Not Sender Correction

State: Existing

Mail from non-local senders appears to be from "daemon" rather than the person who originated the mail.

Patch 120.00

OSF375-350268

Patch: mkpasswd Command Correction

State: Existing

This patch fixes a problem with the mkpasswd command. Hashed password database files (for example, /etc/passwd.pag and /etc/passwd.dir) are deleted before new database files are created.

Patch 121.00

OSF375-350269

Patch: Process Hang On SMP System

State: Existing

Calls to flock() can hang a process on an SMP system if 2 or more processes are attempting to obtain and release an flock() on the same file.

Patch 122.00

OSF375-370036

Patch: Prevent SMP System Duplicate namecache Entries

State: Existing

Problem in DIGITAL UNIX SMP systems where duplicate namecache entries are being created and if heavy file system lookup operations may eventually result in a simple lock timeout and a system panic.

Patch 123.00

OSF375-350273

Patch: rmt Program Correction

State: Existing

This patch fixes a problem that occurs when using the rmt program to access devices or files. The rmt program does not accept reads/writes of less than 1024 bytes. The system displays the following error message:

Cannot set socket receive buffer size

Patch 124.01

OSF375-350275-1

Patch: rlogin Correction

State: Existing

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. DIGITAL has corrected this potential vulnerability.

Patch 125.00

OSF375-350278

Patch: dump/rdump Command Corrections

State: Existing

This patch fixes a problem in dump and rdump. When the -n flag was used, an extraneous file (/dev/:0) was sometimes being created.

Patch 127.00

OSF375-350284

Patch: Asian atty Correction

State: Existing

This patch corrects a problem where a remote user will kill rlogin or telnet and the server host will have an orphaned login process and rlogind or telnetd process in sleep state indefinitely. This is seen only with Asian tty (atty) or any other host which is running c-list rather than STREAMS tty's.

Patch 128.00

OSF375-350285

Patch: more Command Correction

State: Existing

Rectified erroneous behavior of 'more' command when displaying files generated by Oracle.

Patch 129.00

OSF375-350286

Patch: Funnelled Non-Timeshared Thread Correction

State: Existing

This patch fixes a deadlock problem that may occur when a non-timeshared thread becomes funnelled.

Patch 130.00

OSF375-350287

Patch: Correction For floating-point exception

State: Existing

This patch fixes a problem that causes some valid programs compiled with IEEE mode to receive a floating-point exception even though they should run to completion.

Patch 132.00

OSF375-350289

Patch: Compiler Incorrect Codegen Sequence Correction

State: Existing

The code generator used an incorrect codegen sequence when doing stack allocation within procedure prologs where the size of the stack was very large (for example, when a structure is passed as an entity rather than as a pointer).

Patch 134.00

OSF375-350293

Patch: LAT Correction

State: Existing

This patch corrects a problem where processes such as wall, ntalkd, and comsat, when associated with LAT devices, get stuck in the 'u' state (processes are hung) and cannot be cleared from the system.

Patch 136.00

OSF375-350297

Patch: Corrections For Symbolic Link To Root File System

State: Existing

Fixes a problem that causes the system to panic after creating a symbolic link to the root file system ('/') and accessing it like a normal file.

Patch 137.00

OSF375-350298

Patch: Security, (SSRT0362U)

State: Supersedes patches OSF375-350267 (119.00), OSF375-350267-1 (119.01)

This patch corrects the following:

• On systems running enhanced security, the login process may fail with a segmentation fault.

• A security vulnerability has been discovered when running enhanced security that may facilitate unauthorized users gaining access to the system. DIGITAL has corrected this vulnerability.

Patch 139.00

OSF375-350301

Patch: ping Command Correction

State: Existing

This patch fixes a problem in which the ping command can time out after invoking the "rcinet restart" command.

Patch 143.00

OSF375-350306

Patch: Certain Keyboards Stop Functioning After Logout

State: Supersedes patch OSF375-350245 (109.00)

This patch corrects the following:

• On systems with PCXAL, LK411, and similar keyboards, sometimes the keyboard stops working.

• On systems with PCXAL, LK411, and similar keyboards, after logging out of a session on the workstation monitor, sometimes the keyboard stops working. A reboot is required to clear the problem.

Patch 144.00

OSF375-350308

Patch: ATM Correction

State: Existing

This patch prevents a panic that can occur after deleting an ATM ARP entry. The user command to delete an ATM ARP entry is "atmarp -d". Subsequent access to the ATM ARP table can cause the panic.

Patch 147.00

OSF375-350313

Patch: Kernel Memory Fault Panic (svc_auth_unix) Correction

State: Existing

This patch fixes a problem that occurs when the system panics with the following error message:

  kernel memory fault

Patch 150.00

OSF375-350317

Patch: select() Missing State Change Correction

State: Existing

This patch fixes a network socket problem with select() missing state changes on clients from non-write to writable.

Patch 152.00

OSF375-350322

Patch: OSF375-350322

State: Existing

This patch fixes a problem where telnet dumps core if the USER environment variable is the last variable in the environment list.

Patch 157.00

OSF375-350334

Patch: EISA Corrections

State: Existing

This patch fixes two problems that occur on systems with an EISA bus:

• A system running four DE425 adapters off an EISA bus may hang.

• If a device's EISA configuration file contains a function DISABLE keyword and the DISABLE option is selected, the device's driver may not be configured and probed at bus configuration time.

Patch 159.00

OSF375-350336

Patch: Multithreaded Apps Hang On SMP Systems Correction

State: Existing

This patch corrects a problem where multithreaded applications will experience a hang on SMP systems.

Patch 162.00

OSF375X-350019

Patch: User Not Added To New Group

State: Existing

This patch fixes the following problem: If the customer adds a new group with XSysAdmin and then tries to use XIsso to add the user into the new group, the group shows up but the user never gets added.

Patch 163.00

OSF375X-350020

Patch: Slow X Server Performance Drawing Arcs

State: Existing

X server performance is slow when an application is drawing arcs which are outside the bounds of the drawable window.

Patch 165.00

OSF375-350351

Patch: Security, talkd (SSRT0446U)

State: Existing

A potential security vulnerability has been discovered in talkd, where under certain circumstances, system integrity may be compromised. DIGITAL has corrected this potential vulnerability.

Patch 166.00

OSF375X-350023

Patch: dxterm Support To Suppress ANSI Escape Sequences

State: Existing

This patch adds the new resource printOnlyPrintables to dxterm. When this resource is set to TRUE (the default is FALSE), dxterm will not output any escape sequences when printing. This is needed for some PostScript printer (filters) that can not handle escape sequences.

Patch 167.00

OSF375X-350038

Patch: Corrects Memory Leak In The Motif Text Widgets

State: Supersedes patch OSF375X-350035 (201.00)

This patch corrects the following:

• Motif Text widget is afflicted with a memory leak. A small amount of dynamic memory is lost each time the background colors in the widget are changed.

• Motif applications may abort when you use the drag-and-drop feature.

Patch 168.00

OSF375X-350025

Patch: Bookreader Hang Correction

State: Existing

Bookreader hangs when displaying certain pages if the required fonts are not available. This problem usually occurs when redirecting Bookreader's display to another vendor's workstation (HP or Sun).

Patch 173.01

OSF375-360082B-1

Patch: named, screend Corrections

State: Existing

A potential security vulnerability has been discovered in bind, where under certain circumstances users may gain unauthorized access. DIGITAL has corrected this potential vulnerability.

Patch 174.01

OSF375-360082C-1

Patch: uucp Command Corrections

State: Existing

A potential security vulnerability has been discovered in bind, where under certain circumstances users may gain unauthorized access. DIGITAL has corrected this potential vulnerability.

Patch 178.00

OSF375-350345

Patch: UFS 32GB File write Performance Correction

State: Existing

Data written to a file greater than 32 GB in length will be slower than data written to the file when it is less than 32 GB in length.

Patch 179.00

OSF375-360081

Patch: getty Command Option Correction

State: Existing

Allows getty to accept uppercase usernames.

Patch 185.00

OSF375-350362

Patch: mailx Command Corrections

State: Existing

Fixes an error that occurs when replying to a message in which the "CC:" field contains blank-separated names not enclosed in angle brackets ("<...>").

Patch 190.00

OSF375-067

Patch: Potential Data-Corrupt, DE500-AA e-net Adapt

State: Supersedes patch OSF375-048 (48.00), OSF375-066 (189.00)

This patch corrects the following:

• Upgrade/replacement for the ethernet driver when a DE500-AA, containing the DECchip 21140-AC, Fast Ethernet interface is used; allow filtering of greater than 16 multicast addresses and fixes the previous limitations to Hash/Perfect mode filtering.

• Fixes system panics on an SMP system with a tu (Tulip) Ethernet interface with the error message:

  "System Uncorrectable Machine Check 660 (retry set)"
  

• Driver workaround to avoid potential data-corruption problem inherent in the DE500-AA 10/100 Mbps Ethernet adapter.

Patch 193.00

OSF375-350247

Patch: acctcom Command Correction

State: Existing

Fixes a problem in which the size field of a process displayed by the acctcom command is displayed incorrectly.

Patch 199.00

OSF375X-350033

Patch: dxsession Close Button Operation Correction

State: Existing

Fixes problem where exiting from the DECwindows Session Manager (dxsession) via the 'Close' option of the window menu results in an undesirable saving of dxsession's scratch file in /tmp. Use of this button also causes a behavior inconsistent, with dxsession's 'End Session' button.

Patch 209.00

OSF375-360095

Patch: telnetd Correction

State: Existing

Prevents a long delay while trying to log out using telnet.

Patch 210.00

OSF375-370057

Patch: Kernel Builds But Is Not Bootable

State: Existing

Fixes a problem that occurs on AlphaServer 4100 systems in which the kernel will build, but is not bootable.

Patch 212.00

OSF375-360097

Patch: Misc nfs_client Problems

State: Existing

Fixes a problem in which the system crashes when attempting to NFS mount a text file.

Patch 213.00

OSF375-360098

Patch: Pipe Function Correction

State: Existing

Fixes a problem in which the system crashes when attempting to NFS mount a text file.

Patch 218.00

OSF375X-005

Patch: Issues With S3 Trio64/ATI Mach64 Graphics Cards

State: Supersedes patch OSF375X-365003 (161.00), OSF375X-350032 (175.00)

This patch corrects the following:

• On systems with an S3 Trio64V+ graphics card (PB2GA-JC or PB2GA-JD), the X server hangs while drawing the login screen.

• Systems with an S3 Trio64 graphics card can loose time (on the order of a few minutes a day).

• On systems with an ATI Mach64 graphics card, sometimes the monitor will lose synchronization or become stuck in power-save mode.

Patch 220.00

OSF375-350384

Patch: Various Sckt, Net, pcktfltr, panic Corrections

State: Supersedes patches OSF375-350248 (110.00), OSF375-350294 (135.00), OSF375-350305 (142.00), OSF375-350342 (177.00), OSF375-365055 (208.00), OSF375-365057 (233.00)

This patch corrects the following:

• Enhanced fix to the solockpair() routine; problem symptoms include kernel memory faults with sockets, mbufs and mblocks as well as hangs. Applications using sockets in a multi-threaded, multi-cpu environment can experience a number of lock violations with the socket structures.

• Fixes a problem in which packet filter programs do not receive packets when the source is sending multicast packets on an Ethernet network.

• Fixes a problem in which network applications communicating to one of the host's own addresses, may hang, or receive the error message:

  no buffer space available
  

• Fixes situation of a DIGITAL UNIX system connected to a token ring network receiving a ping, not being able to respond and the token ring driver displays "List Error in transmit" message.

• A "panic: lock_read: hierarchy violation in del_dealloc_stg" error occurs when a socket lock is held by a UNIX domain while calling vrele().

• Fixes a system panic caused by a Windows95 or WindowsNT system sending an illegal length ping (ICMP) packet.

• Fixes a kernel memory fault panic that occurs on SMP platforms when running the Unicenter product from Computer Associates in conjunction with Oracle software.

Patch 225.00

OSF375-350405

Patch: SMP "simple_lock: time limit exceeded" Correction

State: Existing

Fixes panics that may occur on SMP systems with message:

"simple_lock: time limit exceeded"

Patch 226.00

OSF375-350407

Patch: Device Driver Corrections

State: Supersedes patch OSF375-350363 (186.00)

This patch corrects the following:

• Fixes a problem in which a system with an HSZ70 controller with a Q-Logic adapter or a KZPSA adapter may experience kernel memory faults during a failover and display a message similar to the following:

  panic (cpu 8): kernel memory fault
  cam_logger: CAM_ERROR entry too large to log!
  

• A custom SCSI driver may return the error ENOMEM from its ccmn_open_unit() routine.

Patch 227.00

OSF375-350410

Patch: File System Incorrect User Type Correction

State: Existing

Fixes a problem that causes an AdvFS file system encapsulated under LSM to appear as a user type of "gen", rather than the correct type, "fsgen".

Patch 231.00

OSF375-360109

Patch: "simple lock time limit exceeded" System Panic

State: Existing

Fixes a problem that occurs on SMP systems using LSM in which the system panics with a "simple lock time limit exceeded" message.

Patch 235.00

OSF375-370055

Patch: Kernel Memory Faults During Booting

State: Existing

Fixes a problem where an AlphaServer 4100 may panic with a kernel memory fault where a system has more than 32 Mb of memory and the console variable MEMORY_TEST is set to "partial".

Patch 237.00

OSF375X-006

Patch: Bookreader UID Handling Correction

State: Supersedes patch OSF375X-350037 (164.00)

• Fixes a problem in which a Bookreader library routine does not restore the effective UID.

• When called from an application, bookreader changes the caller's effective UID to the real UID, but then never restores it to the original effective UID, before returning control to the calling program.

Patch 238.00

OSF375-084

Patch: System Will Not Reboot, System Crash Booting

State: Supersedes patch OSF375-057 (57.00)

This patch corrects the following:

• Fixes problem on AlphaServer 2100A system; when the system is shut down using the "shutdown -r" command, the system will not reboot.

• Alphaserver 2100A system crashes during boot with greater than 1GB of memory installed.

Patch 247.00

OSF375-093

Patch: ar Command Corrections

State: Supersedes patch OSF375-060 (60.00)

This patch corrects the following:

• The ar command is unable to find object modules specified for deletion or extraction whose names are longer than 13 characters.

• This patch fixes a problem with the ar command's -x option, which extracts archive files. Without this fix, the ar command's -x option may, in error, return a message stating that the specified archive file was not found.

Patch 250.00

OSF375-100

Patch: who Command Correction

State: New

Corrects a problem that occurs when more than 140 users are logged on to a system and the who command is issued. If the output from the command is redirected or piped, the last several lines become corrupt.

Patch 253.00

OSF375-104

Patch: rdist Utility Correction

State: New

Correction for rdist Utility to prevent segmentation fault.

Patch 255.00

OSF375-106

Patch: rpc.statd Daemon Corrections, Security (SSRT0456U)

State: Supersedes patch OSF375-350304 (141.00)

This patch corrects the following:

• 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. DIGITAL has corrected this potential vulnerability.

• Fixes a problem that occurs in ASE/TCR environments in which the rpc.statd daemon does not start when using the -p option to specify a long pathname (> 45 characters). When this happens, NFS locking to the NFS service fails causing applications like mail to hang.

Patch 256.00

OSF375-107

Patch: Security, restore (SSRT0490U)

State: New

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. DIGITAL has corrected this potential vulnerability.

Patch 258.00

OSF375-109

Patch: ftp Command Correction, Security (SSRT0505U)

State: Supersedes patch OSF375-350318 (151.00)

This patch corrects the following:

• 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. DIGITAL has corrected this potential vulnerability.

• This patch fixes a problem with the ftp command. If you ftp to an IBM MVS system using the IP address, the IBM system will refuse the connection. This problem can be encountered on any system that validates TOS (Type Of Service) requests if the file /etc/iptos is not used on the client. It is recommended that this patch be installed on all OSF systems.

Patch 263.00

OSF375-114

Patch: Library Corrections

State: Supersedes patch OSF375-350315 (148.00), OSF375-350368 (203.00), OSF375-350374 (205.00)

This patch corrects the following:

• Resolves a hang in the xticlose() routine and a kernel memory fault in the xti_discon_req() routine.

• Fixes a problem for TLI applications which make use of the t_accept library routine. The secondary endpoint state is not being set correctly.

• Corrects a problem encountered by tli applications which do an abort disconnect on an endpoint which was established as an orderly release endpoint and leave the endpoint in an unexpected state.

• Ensures that t_errno is set even when trcv retrieves no data.

Patch 265.00

OSF375-116

Patch: Kernel Memory Fault Panic Correction

State: New

Corrects a problem that occurs on Alpha VME 4/2xx systems. The system may panic and display the following error message:

 kernel access memory fault

Patch 266.00

OSF375-117

Patch: Correction For ufs_fsck, fsck, Prop List Corr

State: Supersedes patches OSF375-350347 (200.00), OSF375-350357 (183.00)

This patch corrects the following:

• Fixes a ufs_fsck problem where ufs_fsck would mishandle certain dir corruptions, recursively asking the user if they want to fix it.

• Fixes fsck operation where if fsck is run on a non-existent file system or on a currently mounted file system, it returns a success status of zero. It should return a non-zero status.

• Fixes a problem in which the UFS property list can become corrupted.

Patch 267.00

OSF375-118

Patch: Corrects Several pcnfsd Problems

State: New

This patch corrects the following:

• Printing from a PC via pcnfsd and logged in as user nobody would report a "file not found" or "access violation" error message.

• When signals causing pcnfsd to terminate or when a SIGPIPE signal was not caught, pcnfsd would exit without producing a core file.

• The pcnfsd authentication would cause crashes and memory corruption.

Patch 269.00

OSF375-350413

Patch: audit_tool Command Correction

State: Existing

The audit_tool command hangs if the audit log contains pathnames that encounter boundary conditions.

Patch 270.00

OSF375-350418

Patch: awk Command Correction

State: Existing

awk consumes memory until the machine swaps itself and core dumps with:

write failed, file system is full  Memory fault - core dumped

Patch 272.00

OSF375-350420

Patch: Security, mountd (SSRT0496U)

State: Existing

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. DIGITAL has corrected this potential vulnerability.

Patch 274.00

OSF375-350423

Patch: doconfig Hang Correction

State: Existing

Fixes a problem the doconfig program hangs after being invoked by the uuxqt program.

Patch 277.00

OSF375-350443

Patch: Linker Corrections

State: Supersedes patches OSF375-360049 (78.00), OSF375-360073 (88.00), OSF375-350337 (160.00)

This patch corrects the following:

• Fixes the following linker problems:

  • Hidden/export symbol wildcard problem

  • Assert getting generated with R_GPVALUE relocations

  • Improper Text segment alignment processing

  • Internal memory managment problem processing C++ program

• This patch fixes a problem where use of "ld -r" will change symbol preemption behavior.

• This patch changes how the linker handles permission problems with chmod(), boundary check for OMAGIC (impure) object files.

• This patch fixes a performance problem that the linker has with hidden symbols (-hidden flag) and large numbers of shared library files (.so files).

Patch 278.00

OSF375-350445

Patch: Out Of Order Packets, Mem Leak Corrections

State: Supersedes patch OSF375-350288 (131.00)

This patch corrects the following:

• Fixes a memory leak problem using the STREAMS Data Link Bridge (dlb) pseudodevice driver and could cause a "freeing free mbuf" panic when system memory is exhausted.

• This patch corrects a problem with packets out of order experienced by some PATHWORKS Netbuei clients.

Patch 281.00

OSF375-350452

Patch: "advfsstat -n" Causes A Core Dump

State: Existing

Fixes an AdvFS problem in which the "advfsstat -n" command causes a core dump. The system displays the message:

Memory fault(coredump)

Patch 284.00

OSF375-370059

Patch: io_zero() System Call Returns An Incorrect Value

State: Existing

Fixes a problem in which the io_zero() system call returns an incorrect value on an AlphaServer 1000.

Patch 290.00

OSF375-360116

Patch: "vquotacheck -a" Erroneously Sets Quotas

State: Existing

Fixes a problem where the AdvFS filesystem command "vquotacheck -a" erroneously sets all quotas for users to values derived from the last AdvFS fileset in /etc/fstab, rather than the correct values for each individual fileset.

Patch 291.00

OSF375-350213

Patch: LSM Volumes Remain in SYNC State

State: Existing

Fixes a problem on ASE systems where LSM volumes remain in SYNC state when no volume resync or volplex att command is running. This results in performance degradation.

Patch 295.00

OSF375-123

Patch: Security, ftpd (SSRT0448U, SSRT0452U)

State: Supersedes patches OSF375-350300 (138.00), OSF375-350335 (158.00), OSF375-121 (293.00)

This patch corrects the following:

• 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. DIGITAL has corrected this potential vulnerability.

• When a user incorrectly logs in using the ftpd command, a "Login incorrect" message is displayed and after ftpd exits, the system will core dump.

• ftpd core dumps when using anonymous ftp with the ls commmand.

Patch 296.00

OSF375-124

Patch: pax, cpio, tar Command Corrections

State: Supersedes patches OSF375-350303 (140.00), OSF375-350333 (156.00), OSF375-350333-1 (156.01), OSF375-350400 (223.00), OSF375-108 (257.00)

This patch corrects the following:

• Fixes the following problems with the pax command when cpio format is used:

  • The cpio -z command hangs the system when small files are read using a large block size.

  • When reading a series of commands, cpio fails on the second command and displays a "No input" error message. If an identical third cpio read is issued, cpio works as expected.

• Fixes a problem where the tar and pax programs incorrectly append files to an existing archive and cause the file to become corrupt.

• Fixes a problem with the tar "tv" command in reporting ownership on a file that had no legitimate owner at the time it was archived. Based on the position of the file in the archive, tar returned the owner of a previous file, or the values -973 for userid and -993 for groupid.

• Fixes pax's tar and cpio archive handling to allow filesizes greater than 4GB.

• The tar(pax) command doesn't correctly handle sparse files, especially Oracle database files. Pre-allocated space is not replaced on restore.

Patch 298.00

OSF375-126

Patch: Kernel Memory Faults, ICMP REDIRECTS Correction

State: Supersedes patch OSF375-063 (63.00)

This patch corrects the following:

• Fixes kernel memory faults in networking code from RTFREE.

• This patch fixes ICMP REDIRECTS. When an ICMP REDIRECT is received, the routing table was updated properly, but the IP layer didn't use the new route information.

Patch 302.00

OSF375-131

Patch: FDDI Driver Corrections

State: Supersedes patches OSF375-350367 (188.00), OSF375-350419 (271.00)

This patch corrects the following:

• Fixes a kernel memory fault caused by the fta FDDI driver.

• Fixes a problem where after a hang the system crashes with the panic message: apecs_read_io_port. At that time, the only way to reboot the system is to switch it OFF then ON.

• Upgrade/Replacement for the "FTA" FDDI driver and fixes a DMA Error which can occur with the older driver.

Patch 304.00

OSF375-133

Patch: network sockets Left In FIN_WAIT_1 State Correction

State: Supersedes patch OSF375-061 (61.00)

This patch corrects the following:

• Fixes a problem of memory corruption. A TCP control structure is illegally accessed after it is released. The corrupted memory buckets are the 256-byte size.

• This patch is a kernel fix for network sockets left in FIN_WAIT_1 state forever. This patch contains a "tunable" kernel parameter. It is recommended that only experienced system administrators attempt to set this parameter from the default value.

Patch 307.00

OSF375-136

Patch: Corrects Printing To Console During A Panic

State: New

Corrects a problem for several platforms that don't print to the console terminal during a panic correctly. The particular platforms involved are AlphaStation 600, AlphaPC 164, AlphaServer 1000A 5/XXX, AlphaServer 1000 5/XXX, AXPvme 100 SBC, and DIGITAL Personal Workstation 433au, 500au, 600au.

Patch 308.00

OSF375-138

Patch: Token Ring Driver Correction

State: Supersedes patch OSF375-058 (58.00), OSF375-103 (252.00)

This patch corrects the following:

• Upgrade/replacement for the Token Ring driver: fixes an intermittent kernel memory fault problem and additional enhancements added to transmit and receive list processing routines to ensure data integrity.

• This patch fixes a Token Ring transmission timeout. The driver can experience "ID 380PCI20001 (8/13/95)" as described in the TI380PCI Errata.

Patch 309.00

OSF375-139

Patch: Corrects file-on-file System mount Panic

State: New

Corrects a problem in which a file-on-file system mount of either an NFS or a /proc file system will panic the system.

Patch 310.00

OSF375-140

Patch: Corrects lpd daemon Start Problem

State: New

Corrects a problem with the lpd line printer daemon when "/sbin/init.d/lpd stop" is followed right away by "/sbin/init.d/lpd start", the new lpd fails to start. The error message from syslog is:

/usr/spool/lpd.lock: locking failed: Operation would block

Patch 325.00

OSF375-156

Patch: Corrects ncheck -s Option Usage Problem

State: New

Corrects an AdvFS problem when running the ncheck utility with the -s option on an AdvFS file system, the command never returns but instead justs keeps using cpu cycles. This problem only occurs when there are no special files in the file system.

Patch 327.00

OSF375-158

Patch: File Lock Corr(s), Filesystem Can Not Be Unmounted

State: Supersedes patches OSF375-350454 (282.00), OSF375-148 (317.00)

This patch corrects the following:

• Fixes a kernel memory fault panic in purge_fs_locks. This problem is normally only seen on ASE or TruCluster systems.

• Fixes several problems with vfs file locking that could cause a crash including the file lock adjust logic, delete sleep lock logic, dead file lock logic, check/change granted logic, and insert file lock logic.

• A filesystem cannot be unmounted and the system displays a "Device busy" error message.

Patch 329.00

OSF375-160

Patch: 4GB Buffer R/W problem, poll() System Call As Timer

State: Supersedes patch OSF375-350397 (222.00)

This patch corrects the following:

• Fixes a read/write problem for buffers larger than 4GB. The read/write request would truncate to a maximum of 4GB, but return success, causing data corruption.

• Adds a mechanism to the poll() system call to allow it to be used as a timer.

Patch 332.00

OSF375-163

Patch: Prevents "kernel memory fault" During Sync Operation

State: New

Prevents a "kernel memory fault" in the bread() routine while performing sync operations.

Patch 336.00

OSF375-168

Patch: Include New Error Reporting Command, filterlog

State: New

This patch provides a new command, filterlog, which improves error reporting on AlphaServer 8200/8400 systems.

Patch 342.00

OSF375-175

Patch: Corrects simple lock timeouts And kern mem Faults

State: New

Corrects a problem on DIGITAL's 8200/8400 machines where cpus may be bombarded with interrupts. The high amount of interrupts may cause simple lock timeouts and kernel memory faults.

Patch 364.00

OSF375-174

Patch: Host MIB and SNMP Correction

State: Supersedes patches OSF375-360066 (84.00), OSF375-360100 (229.00), OSF375-360114 (289.00), OSF375-360054 (82.00), OSF375-153 (322.00)

This patch corrects the following:

• Fixes the os_mibs source file, hrm_fs.c, which makes a call to the statfs function with 2 arguments, when statfs expects 3 arguments.

• Removes support for atTable, so that common applications (like NetView autodiscovery) will use the ipNetToMediaTable instead.

  The SNMP agent returns incorrect data when requested for the MIB II Address Translation Table (atTable). The agent returns correct data for ipNetToMediaTable, which supersedes atTable in MIB II.

• Fixes memory leaks with the FDDI and Token Ring method routines used with Extensible SNMP subagent (ESNMP).

• The Host MIB code uses incorrect presentation names for some processors. This is seen when retrieving the MIB variable "hrDeviceDescr". This patch also adds presentation names for processors added in release v3.2g.

• Allows the extensible SNMP deamon to handle a very high volume of SNMP trap requests.

• Fixes the problem where a malformed trap message sent at boot-time by the DIGITAL UNIX SNMP daemon to a Windows NT Network Management Station (NMS) could cause the NMS application or the NT operating system to crash.

Patch 365.00

OSF375-176

Patch: ed Command Correction

State: New

This patch fixes a problem in which the ed command when used with the -G option prints extra characters.

Patch 368.00

OSF375-180

Patch: vdump & vrestore Command Corrections

State: New. Supersedes patches OSF375-350389 (240.00), OSF375-074 (215.00), OSF375-075 (216.00), OSF375-154 (323.00), OSF375-169 (337.00)

This patch corrects the following:

• Fixes a problem caused by the vrestore command. The command would fail when restoring multiple savesets from a TZS20 tape drive.

• Fixes a problem in which vrestore can cause an occasional core dump (Foating Exception).

• Fixes a problem in which the vrestore command is unable to read data from a raw disk partition.

• Fixes a problem where the vrestore program does not report failed exit status appropriately on incomplete or incorrect commands, corrupt or invalid saved sets, or file open failures.

• Fixes a problem in which the vrestore command fails when running multiple iterations of the command in a script or from the command line.

• Fixes a problem with the vrestore command. The command had returned a success status code even though it had restored an incomplete file during the operation.

Patch 370.00

OSF375-184

Patch: OSF375-184

State: New

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. DIGITAL has corrected this potential vulnerability.

Patch 371.00

OSF375-186

Patch: lpq Print Subsystem Corrections

State: Supersedes patch OSF375-350392 (221.00)

This patch corrects the following:

• Fixes a problem where the lpq command causes the program to crash (segmentation fault).

• Improves the reliability and efficiency of DIGITAL UNIX print services.

Patch 372.00

OSF375-187

Patch: libc And Utility Corrections

State: Supersedes patches OSF375-350217 (93.00), OSF375-350222 (95.00) OSF375-350236 (101.00), OSF375-350253 (114.00), OSF375-350279 (126.00), OSF375-360053 (81.00), OSF375-360082 (180.00), OSF375-360082-1 (244.00), OSF375-350412 (268.00), OSF375-350449 (280.00), OSF375-002 (2.00), OSF375-085 (239.00), OSF375-360064 (83.00), OSF375-101 (251.00), OSF375-110 (259.00), OSF375-111 (260.00), OSF375-152 (321.00), OSF375-236 (415.00)

This patch corrects the following:

• Fixes a problem with the statvfs function. statvfs returns an incorrect status when the file system is full.

• Fixes a problem in which the vquota, vedquota, quota, edquota, dump, csh, and nslookup commands will sometimes display incorrect error messages for non-English locales.

• Fixes a problem in which RPC client functions do not correctly handle system calls interrupted by a signal (EINTR errors).

• Fixes a problem with the auditd daemon. If auditd is logging to a server and the server becomes unavailable, the CPU usage for the daemon rises dramatically.

• This patch allows system managers to both set and obtain quotas for users and groups which are numeric when using the edquota, vedquota, quota and vquota programs.

• Fixes a problem in which the 'date' command is unable to set the date to January 1, 1970 00:00:00 GMT or February 29, 2000.

• Enhancements to the date command for Year 2000 support.

• Fixes a problem where printing of a string with a specified precision could result in a segmentation fault.

• Fixes a TCP/IP problem that can occur with programs linked with the libc library. These programs may return a value of (-1) when calling the svc_tcp() function.

• A potential security vulnerability has been discovered in bind, where under certain circumstances users may gain unauthorized access. DIGITAL has corrected this potential vulnerability.

• /sbin/shutdown takes too long if there are many open LAT lines.

• This patch fixes a problem that occurs after a user logs into a system with an SRV4-style LAT device. When the ttyslot function is called, the system fails to find the device and returns a value of zero, indicating an error in the ttyslot function.

• The patch ensures that setlocale() does not call free() with a null pointer, which may crash an application that uses a third-party malloc package.

• sendmail would generate a core dump with a segmentation fault.

• problem in the filename pattern-matching behavior of the find command when it includes the "?" metacharacter. The bug actually resides in fnmatch(), which is used by find.

• A memory leak problem associated with the strxfrm() and wcsxfrm() functions and some incorrect behavior in __do_replacement(), which is used by both strxfrm() and strcoll().

• Fixes a problem with the edquota utility, which prevented a user from creating quotas for UIDs or GIDs that did not already exist in the /etc/passwd or /etc/group files.

This patch adds automatic detection of a cdfs file system for the mount(8) command.

Patch 374.00

OSF375-189

Patch: ksh Shell Correction

State: Supersedes patch OSF375-350239 (104.00)

This patch fixes the following problems:

• When editor options are set in ksh, ksh would not reset modes when ksh exited via a trap.

• Fixes a problem that was caused by the Korn shell running in EMACS mode. When a window was resized with a width that exceeded 160 characters, the next command (or even a return) would cause the ksh utility to core dump.

Patch 375.00

OSF375-190

Patch: Tape Servicea Relocation Correction

State: New

This patch fixes a problem in which a a cluster member panics, when the Production Server or Available Server software attempts to relocate a tape service.

Patch 376.00

OSF375-191

Patch: machine check Correction

State: New

This patch fixes the following problems that occur on AlphaServer 1000A 4/233 and 4/266 systems:

• If a machine check occurs, the register data written to the binary.errlog will show zeroes in all registers when viewed with DECevent.

• If a correctable memory error occurs, the system panics with a kernel memory fault.

Patch 378.00

OSF375-195

Patch: Correction to Potential Problem to C-library Call

State: New

This patch corrects a potential problem in the handling of a ieee_get_state_at_signal(3) C-library call.

Patch 379.00

OSF375-196

Patch: kloadsrv Will not be haulted in Single-User Mode

State: New

This patch ensures that kloadsrv remains running when the system is shut down to the single user run level.

Patch 380.00

OSF375-197

Patch: AdvFS Corrections

State: Supersedes patches OSF375-047 (47.00), OSF375-360041 (77.00), OSF375-360051 (80.00), OSF375-052 (52.00), OSF375-360067 (85.00), OSF375-360071 (87.00), OSF375-350324 (153.00), OSF375-360088 (197.00), OSF375-360090 (198.00), OSF375-077 (217.00), OSF375-360112 (288.00), OSF375-137 (172.00), OSF375-115 (264.00), OSF375-122 (294.00), OSF375-127 (299.00), OSF375-144 (314.00), OSF375-155 (324.00), OSF375-162 (331.00), OSF375-164 (333.00) OSF375-171 (361.00), OSF375-172 (362.00), OSF375-173 (363.00), OSF375-183 (369.00), OSF375-231 (411.00), OSF375-244 (421.00), OSF375-188 (373.00)

This patch corrects the following:

• Corrects a problem where the mcellCount on-disk was not being updated as files were being migrated and this resulted in a panic situation.

• Fixes AdvFS performance problems.

• Fixes an AdvFS problem that causes a lockmode 4 system panic.

• Corrects a situation where a quotacheck can cause a system panic.

• Fixes a kernel memory fault problem that occurs on AdvFS file systems. The system displays the following error message:

  panic: kernel memory fault at spec_reclaim()
  

• Fixes a problem that occurs on AdvFS file systems where, under certain circumstances, modifications to mmaped data are not written to disk. This may result in data corruption.

• Corrects a problem with domain panics that could possibly cause the system to panic. A new AdvFS error number (E_DOMAIN_PANIC) (-1028) was created.

• Fixes a system panic when shutting down to single user mode using either one of the following commands when AdvFS is the root or usr filesystem:

  # shutdown now
  # init s
  

• Fixes a system panic with the following error message:

  panic (cpu 0): kernel memory fault
  

• Fixes a problem with an NFS V3 mounted AdvFS file system where under heavy I/O load, data written to a file may be lost. Additionally, because file stats are not being saved, the file modification time may revert to a previous value.

• Fixes system panic with the following error message:

  AdvFS exception Module=26 line=1483
  

• Fixes to prevent the following two panics:

  AdvFS Exception  Module = 1, line = 1891
  

  and

  kernel memory fault
  

Patch 380.00

continued

• This patch fixes a problem that occurs with the telnet and ftp commands. Telnet or ftp processes that are no longer in use, are left on the system indefinitely. When a user tries to log in, the login process hangs after displaying the last login message.

• Idle time is reset on broadcast message when AdvFS is the root file system.

• System panics with "kernel memory fault" in ubc_page_alloc().

• A problem in which a system using AdvFS can run out of metadata space when the AdvFS domain still has some free space available. The system will display error messages such as 'no space left on device'.

  The problem may occur on a heavily fragmented system with many small files, such as an Internet News server or Mail server.

• A panic that is seen when running the auditd and auditing msfs_syscall. There will most likely be a lot of memory contention as well for this panic to be triggered.

• A problem in which the getrusage system call returns zero for the values of ru_inblock and ru_outblock on an AdvFS file system.

• Fixes NFS rpc.lockd "can't clear lock after crash of client" when AdvFS is being used.

• Prevents a "kernel memory fault" in the msfs_reclaim() routine on systems using AdvFS.

• Fixes a problem with the chfsets command. When a root user exceeded the fileset quota (which root is allowed to do), the chfsets command reported negative values for the free and available blocks in the fileset.

• Fixes a problem that occurs on AdvFS systems. The system will panic with the following error message:

  malloc_overflow: guard space corruption
  

• Fixes a problem with the AdvFS fs_write routine, which would mishandle partial writes after detecting an error.

• Fixes a problem in AdvFS locking code which causes the following panic:

  kernel memory fault
  

• Fixes a problem in AdvFS. AdvFS does not return an error when a user opens a file in O_SYNC mode and power is lost on the disk drive.

• Corrects a problem where a panic would occur when running rmtrashcan on a clone.

• Fixes a problem with AdvFS, which caused a system panic with the following message:

  log_flush_sync:  pingpg error
  

  The system panic occurred when the AdvFS domain had already issued a domain panic and a user application then attempted to close a file in that domain.

Patch 381.00

OSF375-199

Patch: : Security, crontab (SSRT0487U)

State: Supersedes patches OSF375-350233 (99.00) OSF375-350291 (133.00), OSF375-167 (335.00), OSF375-105 (254.00)

This patch corrects the following:

• The following "at -t" command problems:

  • The command did not work with user id's that were not in the password file.

  • The command did not work on the leap year of 2000.

• Corrects several problems with the "at", "cron", and "crontab" commands.

• 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. DIGITAL has corrected this potential vulnerability.

Patch 383.00

OSF375-201

Patch: High Activity Message Queue Hang Correction

State: New

This patch fixes a problem that occurs with applications based on POSIX message queues. During certain high activity periods, processes may hang when trying to access the message queue.

Patch 384.00

OSF375-202

Patch: File Management, Security (SSRT0537U)

State: New

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. DIGITAL has corrected this potential vulnerability.

Patch 386.00

OSF375-204

Patch: Various Device Driver Corrections

State: Supersedes patches OSF375-370034 (65.00), OSF375-370043 (68.00), OSF375-068 (191.00), OSF375-365052 (192.00), OSF375-350309 (145.00), OSF375-073 (214.00), OSF375-365036 (71.00), OSF375-089 (246.00), OSF375-365068 (285.00), OSF375-095 (248.00), OSF375-112 (261.00), OSF375-141 (311.00), OSF375-161 (330.00)

This patch corrects the following:

• Fixes a problem that occurs when KZPSA and KZTSA hardware resources needed to do I/O are unavailable causing a large number of events to be logged. The system can become sluggish and sometimes crash. This problem is seen on 8400 and 4100 systems with limited hardware scatter-gather memory resources.

• Provides a set of workarounds for Qlogic firmware bugs. These bugs were encountered when using the HSZ70 Raid Array Controller on the KZPBA-CB wide differential UltraSCSI adapter in a dual-node cluster environment.

• Fixes a problem that occurs on AlphaServer 4100 systems. If no devices are attached to the KZPSA disk controller, the system may panic when attempting to perform I/O.

• After a disk error occurs, mirror set switching may not happen soon enough to ensure high availability, or in some cases may not happen at all.

• Provides the following support to DIGITAL UNIX V3.2G:

  • Support the HSZ70 Raid controller on the Fast10 Wide Differential KZPSA adapter in cluster environments under V3.2G. Support of the HSZ70 Raid controller also requires the KZPSA firmware to be upgraded to at least the version distributed on the Version 5.0 AlphaServer Console Firmware CDrom.

  • Performance regression fix for Qlogic isp1020/isp1040 chips.

  • Provide SCSI target mode fixes for ASE/TCR support on QLogic, primarily for HSZ70 support.

  • All modifications included in this patch are compatible with existing versions of KZPSA and Qlogic firmware.

• Adds device recognition for TZ89, TZS20, TZS2, TLZ10, and TLZ1 tape drives.

  sim_err_sm    Target went to command phase
  sim94_intr    Illegal command
   
   panic: "xpt_callback: callback on freed CCB"
  

• Provides support for TZ89, and latent support for TZS20, TZS2, TLZ10, TLZ1.

• When HSZ50 hardware is installed, the system exhibits very slow performance.

• Provides the following additional event logging by the SCSI/CAM disk driver: Additional Unit Attention messages, additional details for hard errors logged after unsuccessful I/O recovery attempts, and provides informational messages on the progress of recovery events.

Patch 386.00

continued

• Fixes various system problems:

  • System panic with: "xpt_callback: callback on freed CCB".

  • System panic with kernel memory fault while trying to remove an spo resource queue entry.

  • Logging following group of 3 errors every few minutes: spo_verify_adap_sanity, spo_misc_errors, spo_bus_reset when the system was under heavy load.

  • A tape drive was powered off for maintenance and disconnected, the HSZ40 was rebooted and the system then panicked with "simple_lock: time limit exceeded".

  • Infrequently, under heavy disk I/O loads, user data can be written to the wrong disk, resulting in data corruption.

• Probe of isp fails intermittently during boot.

• A number of problems have been fixed in the ISP driver. These include: "minimum spl violation" panics with lockmode=4, simple lock time limit restart Qlogic(LUN queue after abort)" panics.

• Fixes a problem in which a failed KZPSA adapter panics the kernel. It also fixes a problem in which CAM status was returning an incorrect "NO HBA" status for miscellaneous SIMPORT errors, instead of the correct "CAM BUSY" status.

Patch 387.00

OSF375-205

Patch: write lock Correction

State: New. Supersedes patch OSF375-178 (367.00)

This patch fixes the following problems:

• Fixes a problem that crashed the system while it was running a "collision" test. The process would hang on a lock, never be woken, and crash the system.

• Fixes a problem in AdvFS that produced the following system panic:

  bs_logflush_start:  cannot write lsn
  

Patch 389.00

OSF375-208

Patch: AdvFS message Correction

State: New

This patch fixes a problem with messages in system logs that reported AdvFS user and group quota limits. The messages were unclear: the user could not determine from them which users or groups were reaching the quota limits.

Patch 390.00

OSF375-209

Patch: System Crashes

State: New

This patch fixes a problem where the machine server system calls are not being type checked properly potentially causing system crashes by unprivileged programs.

Patch 391.00

OSF375-210

Patch: Correction to kloadsrv(8)

State: New

This patch corrects a problem that would randomly cause kloadsrv(8) to crash and improperly load/unload modules.

Patch 397.00

OSF375-216

Patch: Corrects Several rpc.lockd Problems

State: Supersedes patch OSF375-350352 (181.00)

This patch corrects the following:

• NFS mounted file systems may hang.

• The rpc.lockd program may fail because it loses a message granting NLM approval.

• An NFS mounted file system may hang.

• The rpc.lockd daemon may crash with a core dump.

• An error occurs with NFS mounted user mail files. This error prevents the files from being locked and prints out the following message:

  cannot lockf
  

• An NFS problem may occur and the system displays the following error message:

  NFS error 48 cannot bind sockets
  

• Corrects two problems, the first change moves locked files from the message queue to the held list once. The second change adds code to allow locked files leftover from a server reboot, to timeout and be transmitted to the server.

Patch 398.00

OSF375-217

Patch: overflow exception Correction

State: New

This patch fixes a problem that was caused by both floating point and integer overflow exceptions setting the si_code member in the siginfo structure to FPE_FLTOVF.

Patch 400.00

OSF375-219

Patch: Automount Correction

State: New

This patch fixes an automount problem. An automount map file entry that included a comment was being parsed incorrectly, resulting in an error.

Patch 401.00

OSF375-220

Patch: Various NFS Filesystem Handling Correction

State: Supersedes patches OSF375-365034 (70.00), OSF375-365053 (202.00), OSF375-365053-1 (202.01), OSF375-365063 (234.00), OSF375-157 (326.00), OSF375-179 (346.00)

This patch corrects the following:

• 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. DIGITAL has corrected this potential vulnerability.

• Fixes a problem where the umount of a filesystem will fail with "mount device busy", but no processes are accessing files in the filesystem.

• Fix greatly reduces the number of "NFS stale file handle" messages logged to an NFS server system console.

• Allows some third-party NFS v2 clients to experience a performance improvement.

• This patch fixes a problem in which nfsportmon does not allow the root directory to be mounted from either a Solaris system or from an ULTRIX Version 4.2A system.

• Fixes a problem with NFS conversion of a file's vnode number to a file handle number. The file id was truncated improperly, generating EOVERFLOW errors.

Patch 402.00

OSF375-221

Patch: showfile Command Correction

State: New

This patch fixes a problem with the showfile command, which incorrectly returned an error status when it attempted to display a file that was a symbolic link.

Patch 404.00

OSF375-223

Patch: bufpages and bufcache corrections

State: New. Supersedes patch OSF375-213 (394.00)

This patch fixes the following problems:

• Fixes the bufpages calculation so that it takes granularity hints into account.

• Corrects a potential boot panic problem by limiting the size of the bufcache.

Patch 405.00

OSF375-224

Patch: cron Command Problem Correction

State: Supersedes patch OSF375-350390 (241.00)

This patch fixes the following problems:

• Fixes a problem in which the cron command deletes non-local file system files mounted in either the /tmp, /var/tmp, or /var/preserve directories.

• Prevents the crontab file from incorrectly deleting files found in file systems mounted under the /var/preserve, /tmp, and /var/tmp directories.

Patch 406.00

OSF375-226

Patch: syslogd Cannot Write /dev/console, (SSRT0499U)

State: Supersedes patches OSF375-350188 (245.00), OSF375-350383 (219.00), OSF375-099 (170.00), OSF375-128 (300.00), OSF375-143 (313.00), OSF375-222 (403.00)

This patch corrects the following:

• Fixes a problem in which the syslogd daemon may hang when writing to a named pipe log file.

• Fixes a panic that occurs when the system's message buffer size is increased to beyond the default size of 4096. During the subsequent reboot, the syslogd daemon fails with a "Segmentation fault (core dumped)" message, and creates a core file in the "/" directory.

• 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.

• Fixes a problem where the syslogd program cannot properly forward large messages to remote systems. It will either write them to the wrong facility (specified in /etc/syslog.conf) or write incomplete data.

• After a login session on /dev/console exits, syslogd cannot write to /dev/console.

• Fixes a problem in which savecore incorrectly reports a negative number of dumped bytes. This problem may be seen when doing a full crash dump on a system that has more then 2 gigabytes of memory.

• Fixes a problem in which syslogd will core dump if /etc/syslog.auth file has greater than 23 lines.

Patch 407.00

OSF375-227

Patch: Mail Corrections, Security (SSRT0421U)

State: Supersedes patches OSF375-350254 (115.00), OSF375-350331 (154.01)

This patch corrects several mail problems.

• This patch fixes two problems with the mail utility:

  • Mail cannot be sent to usernames consisting of uppercase and lowercase letters.

  • Mail fails when a large distribution list is used.

• Fixes a problem with the sendmail program. Sendmail would dump core and not process any more jobs in the queue when it encountered control characters in a qf file.

Patch 408.00

OSF375-228

Patch: Mem Handling And File System Operation Corr(s)

State: Supersedes patches OSF375-360037 (75.00), OSF375-360050 (79.00), OSF375-049 (49.00), OSF375-050 (50.00), OSF375-056 (56.00), OSF375-350435 (275.00), OSF375-096 (249.00), OSF375-125 (297.00), OSF375-130 (301.00), OSF375-149 (318.00), OSF375-165 (334.00), OSF375-177 (366.00), OSF375-214 (395.00)

This patch corrects the following:

• Fixes a panic in the virtual memory management system. The system displays the following error message:

  trap: invalid memory read access from kernel mode
  

• Fixes the panic "vm_object_free: res count > 1".

• Corrects a problem in which a filesystem may fail to unmount during shutdown or reboot. An error message similar to the following is displayed:

  msfs_unmount EBUSY failed for usr with error 16 during shutdown
  

• Fixes an NFS problem that causes the system to hang.

• Fixes a file corruption problem that may occur with certain applications, for example Realtime applications, that use the plock() system call or the mlock() and mlockall() library routines.

• Fixes a problem that causes systems to panic with a "kernel memory fault" from u_dev_lockop(). This has happened when a database tried to memory map a file.

• This patch fixes a problem in which processes can hang waiting for a system call to table() to complete.

• A problem in which the system will panic with:

  "u_shm_oop_deallocate:   reference count mismatch"
  

• A problem in which the system will panic:

  "pmap_remove_range: page wired"
  

• A PATHWORKS client does not see all the files in a directory when the directory is an NFS mounted OpenVMS UCX exported directory.

• Fixes a problem in which mmap activity to a file that is NFS mounted may cause the client process to hang after the file is deleted.

• Fixes a problem that produced a deadlock betweeen process threads. Typically, the deadlock caused the msfs_getpage routine to wait forever for a lock to be released.

• Prevents a kernel malloc leak when changing the protection of a System V shared memory region that uses gh-chunks.

• Fixes a virtual memory problem in which an uninitialized pointer in u_dev_protect() causes a kernel memory fault to occur.

Patch 409.00

OSF375-229

Patch: Corrections to AdvFS message, linking

State: New. Supersedes patch OSF375-200 (382.00)

This patch fixes the following problems:

• Fixes a problem with an unclear AdvFS message. When trying to mount an AdvFS fileset on a system that did not have AdvFS installed, the following message was displayed:

  No such device
  

  Now, in similar cases, the following AdvFS message is displayed:

  Cannot mount AdvFS fileset, AdvFS not installed
  

• Fixes a problem with AdvFS and links in the /etc/fdmns directory. Previously, AdvFS did not ensure that every link in a directory entry pointed to a block device. Now, it does.

Patch 410.00

OSF375-230

Patch: Correction to a Compiler Problem

State: New

This patch fixes a compiler problem that was causing CPU EXCEPTION errors to be generated in the system binary error log. The problem was experienced during bootstrap on 2100A cpus.

Patch 412.00

OSF375-232

Patch: Corrects Return Error Status For POSIX Compliance

State: New. Supersedes patch OSF375-147 (316.00)

This patch fixes the following problems:

• Corrects the return error status on reads and writes in LSM to make it POSIX compliant.

• Fixes a problem in lsm. A data corruption occurs when readv/writev coallesced via physio while in read/writeback mode.

Patch 413.00

OSF375-233

Patch: Correction to User Stack Pointer Handling

State: New

This patch fixes a problem with user stack pointers not being saved properly in kernel crash dumps for running threads.

Patch 414.00

OSF375-234

Patch: dd Command Corrections

State: Supersedes patches OSF375-350359 (184.00), OSF375-132 (303.00)

This patch corrects the following:

• Fixes a problem when the seek option to the dd command is used to insert data into an existing output file, the resulting file is incorrect and all of the original data is lost.

• Fixes a problem in which the dd command can corrupt output on very large files (2 GB or greater) when the "conv=sparse" option is used.

• Fixes a problem with the dd command in which dd aborts after a read error. This problem occurs even when the "conv=noerror" parameter is specified.

Patch 417.00

OSF375-238

Patch: Various Kernel Corrections

State: Supersedes patches OSF375-055 (55.00), OSF375-360070 (86.00), OSF375-360070-1 (86.01), OSF375-360070-2 (86.02), OSF375-360076 (89.00), OSF375-360076-1 (89.01), OSF375-360085 (187.00), OSF375-365050 (243.00), OSF375-360087 (196.00), OSF375-370048 (207.00), OSF375-350372 (204.00), OSF375-069 (206.00), OSF375-360101 (230.00), OSF375-350438 (242.00), OSF375-365070 (286.00), OSF375-365071 (287.00), OSF375-350448 (279.00), OSF375-119 (283.00), OSF375-120 (292.00), OSF375-135 (306.00), OSF375-150 (319.00), OSF375-151 (320.00), OSF375-211 (392.00), OSF375-215 (396.00)

This patch corrects the following:

• Fixes problems with missing/lost signals that can cause applications to hang. In particular, the DECss7 product may experience severe problems. The problem happens primarily with POSIX signals.

• Corrects a kernel memory fault panic in routine pmap_pt_access().

• Fixes a "simple lock time limit exceeded" panic from the procfs subsystem.

• Fixes a kernel memory fault in the u_anon subsystem.

• Fixes a system crash when setting the date on SMP systems.

• Fixes fixes a problem that occurs when starting up a system that is running the auditing subsystem and the performance manager. The system panics with the error message:

  kernel memory fault
  

• Fixes a problem that may occur after a system panics. The system may hang when trying to do a crash dump.

• Fixes an I/O queue corruption problem that occurs during normal shut down of SMP systems with AdvFS.

• Fixes a problem in which panics will occur if an attempt is made to run a shell script residing on any filesystem mounted with the "noexec" option.

• Fixes the corruption of core files produced by applications with 15 or more threads.

• Fixes three system panics; no special situation that will cause these panics:

  • Fixes a panic that prints "kernel memory fault".

  • Fixes a panic that prints "pmap_dup: level3 PTE not valid".

  • Fixes a panic that prints "delete_pv_entry: mapping not in pv_list".

• Fixes a problem with the exec() system function where a shell script that has "#! " as the first line of the script, invokes the program but does not set the effective user id for the execution of the program.

• Fixes a problem that occurs on AlphaServer 8200 and 8400 systems when a processor fails to restart after a user halts the system by entering "Control-P Control-P" and then typing "continue" on the console.

Patch 417.00

continued

• Fixes problem when debugging multithreaded applications with Ladebug, debugging sessions may hang due to a bug in procfs (e.g., /proc filesystem).

• Fixes system crash when setting the date for SMP systems.

• This patch fixes a problem in which the the lastcomm accounting command doesn't print the "S" flag at appropriate times. This patch also improves the performance of lastcomm.

• This patch enables the latest Informix KAIO functionality. The patch should be installed by Informix customers using the Informix 7.20.UC4 release. The Informix defect number 40041 regarding KAIO is fully addressed by this patch. The patch is required when this message appears, followed by a core dump with the SIGABRT signal:

  Internal AIO consistency error:
  No fork for group completion. Aborting.
  

• Fixes a number of problems relating to signals and POSIX 1003.1b timers in multithreaded programs running on multiprocessor systems. These problems can result in missed timer-expiration signals and system crashes.

• This patch fixes some hangs that can occur during the "syncing disks..." portion of panic processing, improves the reliability of getting a dump after a system panic, and also makes it more likely that AdvFS buffers will be synced to disk after a system panic.

• Removes extraneous debug code.

• Fixes a problem that can cause asynchronous I/O to fail.

• Fixes a problem with the way the ps utility collected CPU usage information. One effect of the problem was that processes run with nice values of 18 or greater had contention problems based on the incorrect CPU values.

Patch 418.00

OSF375-240

Patch: Corr(s) for Kernel, Network, Security (SSRT0476U)

State: Supersedes patches OSF375-370033 (64.00), OSF375-370044 (69.00), OSF375-350252 (113.00), OSF375-350316 (149.00), OSF375-350411 (228.00), OSF375-350422 (273.00), OSF375-350440 (276.00), OSF375-053 (53.00), OSF375-062 (62.00), OSF375-082 (236.00), OSF375-113 (262.00), OSF375-134 (305.00), OSF375-146 (315.00), OSF375-159 (328.00)

This patch corrects the following:

• Fixes a problem that occurs on an SMP system when running STREAMS. The system panics with the following error message:

  "kernel memory fault"
  

  Also the ASDU netbeui server (nbelink) will not close a connection. It will hang in dlcb_close awaiting a STREAMS event. Subsequently, new connections will not be able to connect to nbelink.

• Fixes a problem in the streams code which could have resulted in data corruption.

• Fixes a problem when printing to slow printers using DIGITAL UNIX LAT. The end of a large file fails to print and no error is reported.

• A potential security vulnerability has been discovered, where under certain circumstances, a kernel memory fault panic may occur.

• Fixes a problem that occurs when running STREAMS. The system panics with a kernel memory fault in either osr_run() or osr_reopen().

• This patch fixes a problem that causes the system to panic with a kernal memory fault or "malloc_audit: guard space corruption" with osr_run as an entry in the stack.

• This patch fixes a kernel memory fault panic. This panic occurs on systems running System V applications or any user process compiled with the System V environment, even if System V is not loaded on the system.

• Fixes the problem of a system hang due to corruption of a STREAM synchronization queue's forward pointer. The system hangs in the csq_cleanup() function.

• Fixes the problem where applications running System V pseudoterminal slave pty can hang forever on open() system call.

• Fixes a wide variety of system panics and other problems caused by random memory corruption. Problem noticed at sites hosting a lot of streams activity.

• Allows a customer-written device driver to return the customer's own local error value. Without this patch, the user process will get EINVAL instead.

• Fixes a problem that causes the system to "assert_wait" panic with streams code on the stack.

• Fixes a situation in which the SVR4 STREAMS documentation could be violated. It allows a device number to be pushed on the stream.

• Replace Manual Installation Edit Instructions for OSF375-370033 in setld patch kit.

Patch 418.00

continued

• This patch is an upgrade/replacement for the FAA FDDI driver and fixes a halt/restart problem found in the old driver. The old driver could panic a system with a "simple_lock_fault violation" during a re-initialization.

• Fixes a problem in which the system may panic with the following error message "kernel memory fault".

Patch 419.00

OSF375-241

Patch: cam_tape Panics Correction

State: Supersedes patches OSF375-360052 (194.00), OSF375-360078 (90.00), OSF375-206 (388.00), OSF375-218 (399.00)

This patch corrects the following:

• Fixes a "simple_lock: time limit exceeded" panic.

• Fixes a "simple_lock: time limit exceeded" panic originating from either:

  • ctape_close() routine

  • ctape_strategy() routine

• Fixes a problem where during tape operations, the SPACE commands can not be interrupted.

• Fixes an ASE NFS problem that occurs on ASE systems with KZPBA disk controllers. The system crashes with a "simple_lock timeout" panic.

• Under certain conditions, the message "ctape_strategy: READ case and density info not valid." was being printed for every read from tape. This change will print the message only once.

Patch 420.00

OSF375-243

Patch: Routing Correction

State: New

This patch fixes a routing corruption that could been seen as a kernel memory fault or a corruption within the 128 byte kernel memory bucket.

Patch 422.00

OSF375-246

Patch: sh and rsh Command Corrections

State: Supersedes patch OSF375-350256 (117.00)

This patch fixes the following problems:

• Fixes two problems that occur when an application is started from a subshell, for example, sh -c <command>.

  • An application will hang if it receives an interrupt signal, for example, if the user enters Ctrl/C.

  • While an application is running, if Ctrl/C is entered, the parent process exits, but the child process remains.

• Fixes a problem where the performance of the Bourne shell may be slow when there are many automounted directories in the search path (as defined by the PATH environment variable).

Patch 424.00

OSF375-350230A

Patch: uid/gid From cd_defs Library Function Correction

State: Supersedes patch OSF375-350230 (96.00)

This patch corrects a problem with the cd_defs() function of libcdrom where cd_defs(CD_GETDEFS) returns the wrong default gid and uid for an ISSO 9660 CD-ROM.

Patch 425.00

OSF375-350230B

Patch: Wrong Default uid/gid From cd_defs Library Function

State: Supersedes patch OSF375-350230 (96.00)

This patch corrects a problem with the cd_defs() function of libcdrom where cd_defs(CD_GETDEFS) returns the wrong default gid and uid for an ISSO 9660 CD-ROM.

Patch 426.00

OSF375-350244A

Patch: LSM Configuration Database Corrections

State: Supersedes patches OSF375-350243 (107.00), OSF375-350244 (108.00)

This patch corrects the following:

• A problem in which an LSM configuration database becomes corrupted when it grows beyond 128 KB. The LSM daemon displays an error message similar to the following when it starts up:

  bad magic number
  

• Several problems that occur during certain LSM operations involving disklabel changes.

Patch 427.00

OSF375-350244B

Patch: LSM Corrections

State: Supersedes patches OSF375-350243 (107.00), OSF375-350244 (108.00)

This patch corrects the following:

• A problem in which an LSM configuration database becomes corrupted when it grows beyond 128 KB. The LSM daemon displays an error message similar to the following when it starts up:

  bad magic number
  

• Several problems that occur during certain LSM operations involving disklabel changes.

Patch 428.00

OSF375-350378A

Patch: libcurses tparm Correction

State: Supersedes patch OSF375-350378 (211.00)

Fixes a problem in which the tparm routine in the libcurses.a library does not support more than a three digit value for its input parameter.

Patch 429.00

OSF375-350378B

Patch: libcurses tparm Routine Correction

State: Supersedes patch OSF375-350378 (211.00)

Fixes a problem in which the tparm routine in the libcurses.a library does not support more than a three digit value for its input parameter.