Correction in nbmand behavior [PSARC/2008/584 FastTrack timeout 09/23/2008]

[Rich.Brown at sun.com]

I'm sponsoring this fast track for Afshin Salek (afshin.ardakani at sun.com).

The timer expires on 09/23/2008.

The team requests minor binding.


Template Version: @(#)sac_nextcase %I% %G% SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 Correction in nbmand behavior
    1.2. Name of Document Author/Supplier:
	 Author:  Afshin Salek
    1.3  Date of This Document:
	16 September, 2008
4. Technical Description

         This fast-track proposes a change to the functionality described in
         PSARC 2000/007 "Locking and File Sharing Support" due to the
         incorrect assertion that share reservations and byte range locks
         be checked against each other when the nbmand mount option is set.
         This behavior is not compliant with CIFS semantics and causes CIFS
         protocol errors, which negatively impact the functionality offered
         by the CIFS Service (PSARC 2006/715).  Note that PSARC 2000/007 was
         introduced specifically in support of CIFS.

         Share reservations and byte range locks are not related.  Share
         reservations are only checked when a file is opened, deleted or
         renamed, and are not affected by locks on existing open instances
         of the file.  Byte range locks can be requested after a file has been
         opened successfully but existing share reservations on the open file
         do not affect whether byte range lock requests are granted or denied.
         Byte range locks are only checked against existing locks on the file.

         This fast track proposes that the share reservation and range lock
         cross-checking be removed.  This will only affect system behavior
         when the nbmand option is set.  There is no change in system
	 behavior when nbmand option is not set, as there is no cross-check
	 between share reservations and range locks.

         The change proposed by this fast track does not affect the share
         reservation check algorithm or the byte range lock check algorithm.

6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		ON
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open