Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ufs locking patch released for 4.1B & 4.1C

0 views
Skip to first unread message

KJ Sullivan

unread,
May 9, 1996, 3:00:00 AM5/9/96
to

========= 4.1B ===========
Patch ID : P96050901
Summary : Correction to ufs locking code added by sun patch 100075-09
Status : Mandatory
Date : 05/09/96
Release : OS 4.1B
Architectures : Series5 S4000 Series6
Affected bugs :
2340
Sun bugs: BugId's fixed with this patch: 1077402 1080359 1040406 1046373 1063692
1064183 1071435 1074757 1097368 (exclusive of rpc.lock issues)

Changed files : ufs_lockf.c delta 1.4

Problem Description:

Sun patch 100075-09 was integrated into 4.1B with an incorrect loop increment which
causes a file system locking problem. The problem was detected when a 4.1C filesystem
was exported via NFS to a Solaris 2.X machine. The Solaris system issued the error
message "No network locking on [hostname]". This patch corrects the loop increment
and solves the problem.


======== 4.1C ========

Patch ID : P96022902
Summary : Correction to ufs locking code added by sun patch 100075-09(included in 4.1C)
Status : Mandatory
Date : 02/29/96
Release : OS 4.1C
Architectures : Series5 S4000 Series6
Affected bugs :
2340
Sun bugs: BugId's fixed with this patch: 1077402 1080359 1040406 1046373 1063692
1064183 1071435 1074757 1097368 (exclusive of rpc.lock issues)

Changed files : ufs_lockf.o delta 1.2

Problem Description:

Sun patch 100075-09 was integrated into 4.1C with an incorrect loop increment which
causes a file system locking problem. The problem was detected when a 4.1C filesystem
was exported via NFS to a Solaris 2.X machine. The Solaris system issued the error
message "No network locking on [hostname]". This patch corrects the loop increment
and solves the problem.


These patches can be obtained by contacting Grumman Systems Support
at 1-800-447-2861 or via email to sup...@nts.gssc.com

0 new messages