diff options
author | Pranith Kumar K <pkarampu@redhat.com> | 2019-03-28 17:55:54 +0530 |
---|---|---|
committer | Raghavendra G <rgowdapp@redhat.com> | 2019-03-31 02:56:59 +0000 |
commit | 92ae26ae8039847e38c738ef98835a14be9d4296 (patch) | |
tree | 7c26352f130fc6fecb8ff3063f6bfd7da01152a0 /rpc/rpc-lib | |
parent | 500bd0014128e6727e83b6cb77e8ac94304b8f4a (diff) |
protocol/client: Do not fallback to anon-fd if fd is not open
If an open comes on a file when a brick is down and after the brick comes up,
a fop comes on the fd, client xlator would still wind the fop on anon-fd
leading to wrong behavior of the fops in some cases.
Example:
If lk fop is issued on the fd just after the brick is up in the scenario above,
lk fop will be sent on anon-fd instead of failing it on that client xlator.
This lock will never be freed upon close of the fd as flush on anon-fd is
invalid and is not wound below server xlator.
As a fix, failing the fop unless the fd has FALLBACK_TO_ANON_FD flag.
Change-Id: I77692d056660b2858e323bdabdfe0a381807cccc
fixes bz#1390914
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
Diffstat (limited to 'rpc/rpc-lib')
0 files changed, 0 insertions, 0 deletions