Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#6 chown 07 conflicts with chown 05 #26

Open
denismo opened this issue Jul 20, 2013 · 2 comments
Open

#6 chown 07 conflicts with chown 05 #26

denismo opened this issue Jul 20, 2013 · 2 comments

Comments

@denismo
Copy link
Owner

denismo commented Jul 20, 2013

This is to do with permitPrivilegedOnly. On one hand, one test executes chown under unprivileged user without changing ownership but expects EPERM. On the other hand, other test expects not to get EPERM is ownership does not change

@denismo
Copy link
Owner Author

denismo commented Jul 20, 2013

The current behavior seems to be the most stable as it does not cause other tests to fail:

    def permitPrivilegedOnly(self, block, uid, gid):
        (ouid, unused, unused) = fuse_get_context()
        if ouid and not (uid == -1 or uid == block['st_uid']):
            self.log.debug('permitPrivilegedOnly: owner is not privileged %d => %d, owner %d', block['st_uid'], uid, ouid)
            raise FuseOSError(EPERM)

@denismo
Copy link
Owner Author

denismo commented Jul 20, 2013

In case of an error, the values are like this:
ouid - 65533
uid - 65534
st_uid - 65534

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant