OBSOLETE Patch-ID# 101344-11 Keywords: jumbo NFS patch security panic nfs_bio fopen vnode FDDI argp rename ps Synopsis: OBSOLETED by 101318 Date: Sep/12/94 Solaris Release: 2.3 SunOS release: 5.3 Unbundled Product: Unbundled Release: Topic: SunOS 5.3: Jumbo NFS patch security BugId's fixed with this patch: 1146159 1132302 1141654 1144683 1146065 1146065 1161359 1139146 1153707 1160181 1143962 1157053 1163551 1171950 1172644 Changes incorporated in this version: 1172644 Relevant Architectures: sparc Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: 101318 on Jan/19/99 Files included with this patch: /kernel/fs/nfs /kernel/sys/nfs /usr/lib/fs/nfs/share Problem Description: 1172644 ps(1) very slow on dataless client with 101344-08 installed The ps command (and any references to /proc) were slow due to an unnecessary amount of buffer flushing requests while trying to determine address space sizes. This behavior would only appear on systems with root and /usr partitions mounted remotely over NFS (from 101344-10) 1171950 This patch fixes the bug 1171950, "kernel panics in nfs server during an nfs rename operation" and a similar problem associated with nfs link operation. 1163551 NFS area: file nfs_xdr.c xdr_createargs() doesn't initialize argp->ca_sa. This causes a null pointer reference. (from 101344-09) 1157053 ESC8146 System panics when doing a copy to NFS file system mounted across FDDI-S system panics when doing a copy to NFS file system mounted across FDDI. Copying a 1 meg file causes a panic in xdr_writeargs(). Over ethernet this problem does no happen. (from 101344-08) 1153707 s1093 panic vn_rele: vnode ref count 0 1160181 2.3 system hang due to kernel out of resources (rmalloc_wait()) 1143962 client hangs when a single page cannot be pushed to a server It is possible for the system to hang or panic in certain situations while using remotely mounted filesystems. (from 101344-07) 1139146 fopen(fn,a/a+) in a non-writeable file did not return NULL write(2) to an NFS mounted file, opened with O_CREAT flag, do not fail when file has read-only permission. (from 101344-06) 1161359 machine panic in nfs_bio by user application A user can crash the machine by running two versions of his application. The application mmaps numeric data files that have been automounted from a remote host and does calcuations on the data. If the user runs two versions of his program at the same time, it will crash. Simple user programs that opens the nfs file, mmaps and closes panics the system in nfs_bio(). (from 101344-05) 1146065 authern_marshal crash on diskless ss10 from a 20-way dragon server. The modifications here address the problem of unsafe handling of the cached credential that the NFS client uses. The changes are to correct the handling so that it is mt-safe. (from 101344-04) 1144683 nfs_inactive rfree causes mutex_exit - lock not held panic 1146065 authern_marshal crash on diskless ss10 from a 20-way dragon server. The modifications here address two problems. The first problem is an mt-unsafe condition in the NFS client. It has to do with the way that rnodes are allocated and freed. It was possible for a client to be in the process of releasing an rnode and have it picked up by another thread before the first thread was finished with the rnode. The second problem is some unsafe handling of the cached credential in the rnode. This cached credential is used to pass credential information around between the various layers in the NFS client. The handling of the credential was not mt-safe and so could result in client crashes. (from 101344-03) 1141654 bin access is possible It is possible to create setuid/setgid programs on a server from an insecure client. (from 101344-02) 1132302 read and write data across 5.1 and 4.1.3 NFS fails intermittently This is an NFS data corruption problem in which clients are sometimes unable to read back data that was just written to the server. This is usually characterized by the term, short read. (from 101344-01) 1146159 du, tar, bar does not work with VMS(NFS) fs due to conflicting fileoffset defs The NFS protocol specifies that a NFS_READDIR request return an opaque 32 bit cookie which is used to get the next directory entry. Solaris places this cookie in the directory offset field for use by seekdir() and other directory functions. However, some OSes such as VMS use negative numbers as cookies which causes a seekdir() on the directory to fail. The fix is to allow arbitrary seeks on NFS mounted directories. Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- reboot after installation. Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Installpatch will backout the patch
to leave the system in its pre-patched state. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Error message:
Pkgadd of package failed with error code .
Will not backout patch...patch re-installation.
Warning: The system may be in an unstable state!
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
the patch packages failed. Installpatch will NOT backout the
patch. You may manually backout the patch using backoutpatch,
then re-apply the entire patch. Look in the log file for the
reason pkgadd failed. Correct the problem and re-apply the
patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Message:
Re-installing Patch.
Explanation: The patch has already been applied, but there is
at least one package in the patch that could be added. For
example, if you applied a patch that had both Openwindows and
Answerbook components, but your system did not have Answerbook
installed, the Answerbook parts of the patch would not have
been applied. If, at a later time, you pkgadd Answerbook, you
could re-apply the patch, and the Answerbook components of the
patch would be applied to the system.
Message:
Installpatch Interrupted.
Installpatch is terminating.
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files and exit.
Message:
Installpatch Interrupted.
Backing out Patch...
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files, backout the patch, and exit.
Patch Backout Errors:
---------------------
Error message:
prebackout patch exited with return code .
Backoutpatch exiting.
Explanation and corrective action: the prebackout script
supplied with the patch exited with a return code other
than 0. Generate a script trace of backoutpatch to determine
why the prebackout script failed. Correct the reason for
failure, and re-execute backoutpatch.
Error message:
postbackout patch exited with return code .
Backoutpatch exiting."
Explanation and corrective action: the postbackout script
supplied with the patch exited with a return code other than
0. Look at the postbackout script to determine why it failed.
Correct the failure and, if necessary, RE-EXECUTE THE
POSTBACKOUT SCRIPT ONLY.
Error message:
Only one service may be defined.
Explanation and corrective action: You have attempted to specify
more than one service from which to backout a patch. Different
services must have their patches backed out with different
invocations of backoutpatch.
Error message:
The -S and -R arguments are mutually exclusive.
Explanation and recommended action: You have specified both a
non-native service to backout, and a package installation root.
These two arguments are mutually exclusive. If backing out a
patch from a non-native usr partition, the -S option should be
used. If backing out a patch from a client's root
partition (either native or non-native), the -R option
should be used.
Error message:
The service cannot be found on this system.
Explanation and recommended action: You have specified a non-
native service from which to backout a patch, but the
specified service is not installed on your system. Correctly
specify the service when backing out the patch.
Error message:
Only one rootdir may be defined.
Explanation and recommended action: You have specified more than
one package install root using the -R option. The -R option
may be used only once per invocation of backoutpatch.
Error message:
The directory cannot be found on this system.
Explanation and recommended action: You have specified a
directory using the -R option which is either not mounted,
or does not exist on your system. Verify the directory name
and re-backout the patch.
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: You have attempted to backout
a patch that is not applied to this system. If you must
restore previous versions of patched files, you may have to
restore the original files from the initial installation CD.
Error message:
Patch has not been successfully applied to this system.
Will remove directory
Explanation and recommended action: You have attempted to back
out a patch that is not applied to this system. While the
patch has not been applied, a residual
/var/sadm/patch/ (perhaps from an unsuccessful
installpatch) directory still exists. The patch cannot be
backed out. If you must restore old versions of the patched
files, you may have to restore them from the initial
installation CD.
Error message:
This patch was obsoleted by patch .
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: You are attempting to backout
patches out of order. Patches should never be backed-out out
of sequence. This could undermine the integrity of the more
current patch.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used.
The original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev, cpio