fs/unionfs/copyup.c | 29 +++++++++++++++++++++++------
fs/unionfs/rename.c | 25 ++++++++++++++++---------
2 files changed, 39 insertions(+), 15 deletions(-)
New commits:
commit e07dec8f870f65fd76af5cb8732efedcfb01480f
Author: Erez_Zadok <[EMAIL PROTECTED]>
Date: Mon Jul 9 20:19:08 2007 -0400
unionfs: better handling when copying up permissions
When we copyup a file, directory, or symlink, we may be copying up from one
file system type to another. The destination file system may not support
all of the features of the source file system, and the differences in
support may be minor. For example jffs2 doesn't allow one to chmod a
symlink (and it returns a -EOPNOTSUPP). So we ignore such harmless errors,
rather than propagating them up, which results in copyup errors and errors
returned back to users.
Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>
commit 96c80df29c857245677fa5025424cec2e46e901d
Author: Erez_Zadok <[EMAIL PROTECTED]>
Date: Mon Jul 9 20:14:41 2007 -0400
Unionfs: better error handling in rename code when copyups are involved
First, rewrite code slightly and document it better to explain why we appear
to ignore copyup errors (because we try the next branch to the left).
Second, change a BUG_ON to a printk(KERN_ERR), because a mild failure to
copyup a file should not cause an oops. For example, some file systems
don't support UIDs/GIDs (e.g., VFAT) and others don't allow you to chmod a
symlink (e.g., jffs2), possibly resulting in mild copyup failures; that
shouldn't be considered so severe as to cause an oops.
Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>
_______________________________________________
unionfs-cvs mailing list: http://unionfs.filesystems.org/
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs-cvs
