new delegated attribute functionality question

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

 



Hi folks,

Could somebody explain if there is a problem here or this is really
how things are going to be?

Client opens a file for read and gets a delegation.
Something happens on the server to trigger a cb_recall (another client
access, local access, doesn't matter).

Old code:
cb_recall call
cb_recall reply
delegreturn call
delegreturn reply
We are done.

New code:
cb_recall call
cb_recall reply
open call sent with "claim_deleg_cur_fh" ??? why is the client sending this
open reply
delegreturn call
delegreturn reply

Now because the server is invalidating/revoking the delegation state.
what this could end up turning into is (re-writing all step for show)
cb_recall call
cb_recall reply
open call with claim_deleg_cur_fh
open reply with err_revoked or err_bad_stateid
test_stateid call (testing delegation stateid) again why we got the
cb_recall delegation isn't valid obviously
test_stateid reply stating it's revoked
free_stateid call
free_stateid reply
open call with claim_fh
open reply
delegreturn call
delegreturn reply

We went from 2 RPCs to 6 RPCs? That seems rather bad. Is doing open
claim_deleg_cur_fh a bug?

Thank you.




[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