Questions Regarding Delegation Claim Behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

My name is Petro Pavlov, I'm a developer at VAST.

I have a few questions about the delegation claim behavior observed in the
Linux kernel version 3.10.0-1160.118.1.el7.x86_64.

I’ve written the following test case:

   1. Client1 opens *file1* with a write delegation; the server grants both
   the open and delegation (*delegation1*).
   2. Client1 closes the open but does not return the delegation.
   3. Client2 opens *file2* and also receives a write delegation (
   *delegation2*).
   4. Client1 then issues an open request with CLAIM_DELEGATE_CUR,
   providing the filename from step 3 *(file2*), but using the delegation
   stateid from step 1 (*delegation1*).
   5. The server begins a recall of *delegation2*, treating the request in
   step 4 as a normal open rather than returning a BAD_STATEID error.

My understanding is that the server should have verified whether the
delegation stateid provided actually belongs to the file being opened.
Since it does not, I expected the server to return a BAD_STATEID error
instead of proceeding with a standard open.


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux