[gvfs] fuse: Don't map EISDIR to EXDEV when renaming



commit 232d6d76029dc1cbc0c76c2459f9db26b7717d28
Author: Ross Lagerwall <rosslagerwall gmail com>
Date:   Sat Aug 9 23:14:18 2014 +0100

    fuse: Don't map EISDIR to EXDEV when renaming
    
    vfs_rename incorrectly maps EISDIR to EXDEV when renaming.  However,
    EISDIR occurs when the source is a file and the destination is a
    directory and it shouldn't be remapped.  (G_IO_ERROR_WOULD_RECURSE is
    mapped to EXDEV instead.)
    
    https://bugzilla.gnome.org/show_bug.cgi?id=734568

 client/gvfsfusedaemon.c |    6 ------
 1 files changed, 0 insertions(+), 6 deletions(-)
---
diff --git a/client/gvfsfusedaemon.c b/client/gvfsfusedaemon.c
index 12bcebb..3571930 100644
--- a/client/gvfsfusedaemon.c
+++ b/client/gvfsfusedaemon.c
@@ -1651,12 +1651,6 @@ vfs_rename (const gchar *old_path, const gchar *new_path)
           g_mutex_unlock (&fh->mutex);
           file_handle_unref (fh);
         }
-
-      if (result == -EISDIR)
-        {
-          /* This makes e.g. 'mv' fall back to a recursive copy + delete operation */
-          result = -EXDEV;
-        }
     }
   else
     {


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]