diff options
author | Raghavendra G <raghavendra@gluster.com> | 2011-07-15 01:54:31 +0000 |
---|---|---|
committer | Anand Avati <avati@gluster.com> | 2011-07-29 01:30:28 -0700 |
commit | be817019cbb096fe2cca632c6fbcf77f360e201d (patch) | |
tree | 4e9b071ebb12fb4049ae6fbff68c3654af48eb82 /libglusterfsclient | |
parent | 426c6e6b24748c0826cc97e8f736bc87a1c8df04 (diff) |
performance/quick-read: Handle unwinding of frame corresponding to read fop properly, while validating cache.
- there was a possibility of double unwind in case of errors.
- use a new frame to do open in fd-based fops.
In case of errors, qr_resume_pending_ops will be called to resume all the
fops waiting on open. Hence if we use frame corresponding to fop (without
creating a new one), there is a possibility of frame being freed by the
time open would've returned to quick-read.
Change-Id: Ie4cc19907f9d6362860bdb984779c8f4cf822332
BUG: 3168
Signed-off-by: Raghavendra G <raghavendra@gluster.com>
Reviewed-on: http://review.gluster.com/35
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Anand Avati <avati@gluster.com>
Diffstat (limited to 'libglusterfsclient')
0 files changed, 0 insertions, 0 deletions