diff options
| author | Raghavendra G <raghavendra@gluster.com> | 2011-07-20 11:07:13 +0530 |
|---|---|---|
| committer | Anand Avati <avati@gluster.com> | 2011-07-29 01:29:04 -0700 |
| commit | 6a03c6c49c277d5dcf4ed9d4904361fe7ef305f7 (patch) | |
| tree | 87ea0a262ba677a4508d27b74a523da1c543061c /mod_glusterfs | |
| parent | b221477eb60b22f2cbe994568f76f35b78369e24 (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: I45a528e02b0886d22161ac24ab3e147a26d5ee7d
BUG: 3168
Reviewed-on: http://review.gluster.com/53
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Anand Avati <avati@gluster.com>
Diffstat (limited to 'mod_glusterfs')
0 files changed, 0 insertions, 0 deletions