diff options
author | Steven J. Magnani <steve.magnani@digidescorp.com> | 2019-08-27 15:13:59 +0300 |
---|---|---|
committer | Jan Kara <jack@suse.cz> | 2019-08-27 16:38:46 +0300 |
commit | c3367a1b47d590f97109cd4b5189e750fb26c0f1 (patch) | |
tree | 8f29eb87d3375f3ff048b3384bef9692bde86367 /fs/gfs2 | |
parent | 8cbd9af9d208b1f015cf8a4645602f0a007270a8 (diff) | |
download | linux-c3367a1b47d590f97109cd4b5189e750fb26c0f1.tar.xz |
udf: augment UDF permissions on new inodes
Windows presents files created within Linux as read-only, even when
permissions in Linux indicate the file should be writable.
UDF defines a slightly different set of basic file permissions than Linux.
Specifically, UDF has "delete" and "change attribute" permissions for each
access class (user/group/other). Linux has no equivalents for these.
When the Linux UDF driver creates a file (or directory), no UDF delete or
change attribute permissions are granted. The lack of delete permission
appears to cause Windows to mark an item read-only when its permissions
otherwise indicate that it should be read-write.
Fix this by having UDF delete permissions track Linux write permissions.
Also grant UDF change attribute permission to the owner when creating a
new inode.
Reported by: Ty Young
Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
Link: https://lore.kernel.org/r/20190827121359.9954-1-steve@digidescorp.com
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/gfs2')
0 files changed, 0 insertions, 0 deletions