[
https://issues.apache.org/jira/browse/HDFS-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179033#comment-13179033
]
Brian Bloniarz commented on HDFS-1841:
--------------------------------------
Thanks for taking a look; yeah, you're right that (2) alone is enough to fix
the issue.
I've attached an updated patch which only does that; I also fixed the paths so
that it applies against hadoop trunk. Thanks!
> Enforce read-only permissions in FUSE open()
> --------------------------------------------
>
> Key: HDFS-1841
> URL: https://issues.apache.org/jira/browse/HDFS-1841
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: contrib/fuse-dfs
> Affects Versions: 0.20.2
> Environment: Linux 2.6.35
> Reporter: Brian Bloniarz
> Priority: Minor
> Attachments: patch.fuse-dfs, patch.fuse-dfs.kernel
>
>
> fuse-dfs currently allows files to be created on a read-only filesystem:
> $ fuse_dfs_wrapper.sh dfs://example.com:8020 ro ~/hdfs
> $ touch ~/hdfs/foobar
> Attached is a simple patch, which does two things:
> 1) Checks the read_only flag inside dfs_open().
> 2) Passes the read-only mount option to FUSE when ro is specified on the
> commandline. This is probably a better long-term solution; the kernel will
> enforce the read-only operations without it being necessary inside the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
