All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Michael j Theall <mtheall@us.ibm.com>,
	fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [fuse-devel] [RFC] fuse: Support posix ACLs
Date: Fri, 01 Jul 2016 12:37:15 -0700	[thread overview]
Message-ID: <87a8i19ml0.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <20160630165414.GB123267@ubuntu-hedt> (Seth Forshee's message of "Thu, 30 Jun 2016 11:54:14 -0500")

On Jun 30 2016, Seth Forshee <seth.forshee@canonical.com> wrote:
> Yes, I've already written pretty much the same code and am attempting to
> test it.  The problem I'm having is finding a good filesystem to test
> with. fusexmp works but is probably unfair as the underlying filesystem
> is handling the acls and updating the mode. I haven't found any
> filesystem yet that fully supports xattrs but doesn't do something
> special with the posix acl xattrs.
>
> Can anyone suggest a good filesystem for me to test with?

S3QL should do it with a small patch - at the moment it deliberately
returns an error when the kernel tries to acces system.posix_acl*. This
is done specifically so that the kernel doesn't think that ACLs are
supported when they actually aren't (because of the missing
synchronization with the permission bits).

Download from https://bitbucket.org/nikratio/s3ql/ and comment out the
check in src/s3ql/fs.py:getxattr():

        # http://code.google.com/p/s3ql/issues/detail?id=385
        elif name in (b'system.posix_acl_access',
                      b'system.posix_acl_default'):
            raise FUSEError(ACL_ERRNO)



Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

  reply	other threads:[~2016-07-01 19:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 19:07 [RFC] fuse: Support posix ACLs Seth Forshee
2016-06-29 19:24 ` Michael j Theall
     [not found]   ` <OFF8F0F486.DB2CEB73-ON86257FE1.006A1FF4-86257FE1.006A9703-8eTO7WVQ4XIsd+ienQ86orlN3bxYEBpz@public.gmane.org>
2016-06-29 19:52     ` Michael j Theall
2016-06-29 21:03       ` [fuse-devel] " Seth Forshee
2016-06-29 21:13         ` Michael j Theall
2016-06-29 20:18   ` [fuse-devel] " Eric W. Biederman
     [not found]     ` <87vb0rhhpr.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-06-29 20:35       ` Michael j Theall
2016-06-30  7:23     ` [fuse-devel] " Jean-Pierre André
2016-06-30 13:07     ` Seth Forshee
2016-06-30 16:25       ` Eric W. Biederman
2016-06-30 16:54         ` Seth Forshee
2016-07-01 19:37           ` Nikolaus Rath [this message]
2016-07-01 19:33     ` Nikolaus Rath
2016-07-01 19:49       ` Seth Forshee
2016-06-29 20:56   ` Seth Forshee
2016-06-30  7:13 ` Jean-Pierre André
2016-07-01 19:29 ` Nikolaus Rath
2016-07-01 19:58   ` Seth Forshee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8i19ml0.fsf@thinkpad.rath.org \
    --to=nikolaus@rath.org \
    --cc=ebiederm@xmission.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mtheall@us.ibm.com \
    --cc=seth.forshee@canonical.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.