Windows: 1.5.77 Change Log summary

Change-Id: Ic0362956470ddb76fac64d21927b3e51b7980ea6
Reviewed-on: http://gerrit.openafs.org/2710
Reviewed-by: Jeffrey Altman <jaltman@openafs.org>
Tested-by: Jeffrey Altman <jaltman@openafs.org>

diff --git a/doc/txt/winnotes/afs-changes-since-1.2.txt b/doc/txt/winnotes/afs-changes-since-1.2.txt
index cc1b1c2..ecf23d0 100644 (file)
--- a/doc/txt/winnotes/afs-changes-since-1.2.txt
+++ b/doc/txt/winnotes/afs-changes-since-1.2.txt
@@ -1,3 +1,62 @@
+Since 1.5.76
+ * When the SYSTEM account is in use, the SMB connection is
+   not always established as S-1-5-18.  Sometimes it uses an
+   anonymous, S-1-5-7, connection.  In both cases the SMB
+   authentication name is the nul string.  To better identify
+   when an SMB connection is local system, the smb_username_t
+   is now stored as a SID instead of a user name.  When a SID
+   is used, a new flag bit is set SMB_USERNAMEFLAG_SID.
+
+   In smb_SetToken if AFS_PIOCTL_AFSLOGON is set and the user
+   connection is not SYSTEM, the RPC SID is checked.  If RPC
+   SID is SYSTEM, that supercedes the SMB authentication.
+
+ * Replace STATUS_IO_TIMEOUT with RPC_NT_SERVER_TOO_BUSY for
+   CM_ERROR_ALLBUSY.
+
+ * Replace STATUS_PATH_NOT_FOUND with RPC_NT_SERVER_UNAVAILABLE
+   for CM_ERROR_ALLOFFLINE and CM_ERROR_ALLBUSY.
+
+ * Optimize behavior of buf_CleanAsyncLocked().  Avoid searching
+   for the cm_scache_t object by FID if it is already known.
+
+ * If the readonly file attribute is set (stored as a unix mode)
+   then a CreateFile operation should fail if the file is opened
+   for DELETE in combination with any other privilege.
+
+ * If the directory buffer contents are garbage we can crash
+   the service.  Add some simple validation checks to ensure
+   that cm_dirEntry_t objects have the correct flag value and
+   that the name strings are not too long.
+
+ * If the bulkStat errorCode indicates that a particular object
+   is inaccessible due to a VIO error, we must update the server
+   status appropriately in order to permit failover.
+
+ * An RX_MSGSIZE error is returned by the new PMTU detection
+   code.  It is critical that such an error result in a retry of
+   the operation that failed.  Otherwise, the PMTU detection can't
+   work and the server will be marked down.
+   Secondly, it is important that such errors not leak to the
+   application layer.  Map them to CM_ERROR_RETRY in all cases.
+
+ * Translate RX_RESTARTING to the same cache manager error code
+   for all RPC classes.
+
+ * When logging server volume instance errors to the windows
+   application event log, be sure to log the cell as well.
+   Translating from server ip address is non-trivial.  Make it
+   easier for administrators triaging issues to plug the volume
+   and cell info into vos commands.
+
+ * Since unix mode bits are represented in octal in most cases
+   make sure we log them that way.
+
+ * The cm_enforceTrailingDot() function failed if there was a
+   trailing dot followed by white space.
+
+ * Rx: Do not send RX_MSGSIZE if the PMTU size did not change.
+
 Since 1.5.75
  * A crash could occur if a single letter share name was
    dynamically evaluated as matching a cell name.  This was