path: root/xlators/mount/fuse/src/fuse-helpers.c
diff options
authorKaleb S. KEITHLEY <>2014-08-28 12:33:01 -0400
committerKaleb KEITHLEY <>2014-09-02 04:30:47 -0700
commit1d4ef0b891899e3a6dbc8c2087e73cee6f5a7fbe (patch)
treeffecc156761ac38cbd2ed48d8fc0af0b7dac26f1 /xlators/mount/fuse/src/fuse-helpers.c
parentf0ddba7e0913db505f1295e9b3b7d35ead9c4407 (diff)
mount/fuse: Handle fd resolution failuresv3.4.6beta1
Backport from, 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 <> Reviewed-on: Tested-by: Gluster Build System <> Reviewed-by: Raghavendra G <>
Diffstat (limited to 'xlators/mount/fuse/src/fuse-helpers.c')
1 files changed, 0 insertions, 2 deletions
diff --git a/xlators/mount/fuse/src/fuse-helpers.c b/xlators/mount/fuse/src/fuse-helpers.c
index c5c0404..0b903ee 100644
--- a/xlators/mount/fuse/src/fuse-helpers.c
+++ b/xlators/mount/fuse/src/fuse-helpers.c
@@ -22,8 +22,6 @@ fuse_resolve_wipe (fuse_resolve_t *resolve)
GF_FREE ((void *)resolve->bname);
- GF_FREE ((void *)resolve->resolved);
if (resolve->fd)
fd_unref (resolve->fd);