summaryrefslogtreecommitdiffstats
path: root/THANKS
diff options
context:
space:
mode:
authorKaleb S. KEITHLEY <kkeithle@redhat.com>2014-08-28 12:33:01 -0400
committerKaleb KEITHLEY <kkeithle@redhat.com>2014-09-02 04:30:47 -0700
commit1d4ef0b891899e3a6dbc8c2087e73cee6f5a7fbe (patch)
treeffecc156761ac38cbd2ed48d8fc0af0b7dac26f1 /THANKS
parentf0ddba7e0913db505f1295e9b3b7d35ead9c4407 (diff)
mount/fuse: Handle fd resolution failuresv3.4.6beta1
Backport from http://review.gluster.org/#/c/8402, BZ 1126048 Problem: Even when the fd resolution failed, the fop is continuing on the new graph which may not have valid inode. This lead to NULL layout subvols in dht which lead to crash in fsync after graph migration. Fix: - Remove resolution error handling in FUSE_FOP as it was only added to handle fd migration failures. - check in fuse_resolve_done for fd resolution failures and fail the fop right away. - loc resolution failures are already handled in the corresponding fops. - Return errno from state->resolve.op_errno in resume functions. - Send error to fuse on frame allocation failures. - Removed unused variable state->resolved - Removed unused macro FUSE_FOP_COOKIE Change-Id: I3f3129b9b4fc34ff1fe07218e6924a027346a95e BUG: 1123289 Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com> Reviewed-on: http://review.gluster.org/8562 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
Diffstat (limited to 'THANKS')
0 files changed, 0 insertions, 0 deletions