none
pid context in SMB2 locking? RRS feed

  • Question

  • SMB2 lock requests don't have a pid field like SMB locking does. How are the different locking contexts for different client processes communicated to a server using SMB2 ?

    Cheers, Tridge

    Wednesday, May 21, 2008 1:53 AM

Answers

  •  

    Tridge,

     

        Thanks for your question.   Byte range locks in SMB2 are associated with the handle (SMB2 File ID) on which the lock is taken. Read/write/lock requests using the same SMB2 File ID will not conflict. However, I/O on a different handle (a different SMB2 File ID) will conflict. It is the client's responsibility to locally resolve lock conflicts across multiple processes on the same client, if any such conflicts exist.  We will add the information into section 2.2.6  of the future version of [MS-SMB2].

     

    Thanks

    Hongwei Sun - MSFT

    We're hiring


    hongwei
    Thursday, June 26, 2008 9:10 PM

All replies

  • Thanks for your posting regarding SMB2 locking command.  We'll review your question and post the result of our investigation.  

    Tuesday, May 27, 2008 9:09 PM
  •  

    Tridge,

     

        Thanks for your question.   Byte range locks in SMB2 are associated with the handle (SMB2 File ID) on which the lock is taken. Read/write/lock requests using the same SMB2 File ID will not conflict. However, I/O on a different handle (a different SMB2 File ID) will conflict. It is the client's responsibility to locally resolve lock conflicts across multiple processes on the same client, if any such conflicts exist.  We will add the information into section 2.2.6  of the future version of [MS-SMB2].

     

    Thanks

    Hongwei Sun - MSFT

    We're hiring


    hongwei
    Thursday, June 26, 2008 9:10 PM