On Mon, Feb 13, 2012 at 11:42:49AM +0100, Manuel Bouyer wrote:
> And what happens if you write "baz.foo.bar" ? You could just error out in
> this case.
You are right. If the purpose of -o stripxattr is to let us use a disk from
FreeBSD without damages, then the option should make it impossible to
On Mon, Feb 13, 2012 at 10:37:25AM +, Emmanuel Dreyfus wrote:
> On Mon, Feb 13, 2012 at 11:27:29AM +0100, Manuel Bouyer wrote:
> > But then, if you see USER "foo.bar" in the filesystem, you don't know
> > if it should be mapped to user.foo.bar or foo.bar.
> > I don't think this can work.
>
> I
On Mon, Feb 13, 2012 at 11:27:29AM +0100, Manuel Bouyer wrote:
> But then, if you see USER "foo.bar" in the filesystem, you don't know
> if it should be mapped to user.foo.bar or foo.bar.
> I don't think this can work.
If the disk is from FreeBSD, you mount with -o stripxattr. When
you read it, U
On Fri, Feb 10, 2012 at 02:01:58PM +0100, Emmanuel Dreyfus wrote:
> [...]
> I think we just need a mount option: -o -stripxattr
> It would do this mapping:
> "system.foo" <-> SYSTEM "foo"
> "trusted.foo" <-> SYSTEM "trusted.foo"
> "security.foo" <-> SYSTEM "security.foo"
>
On Mon, Feb 13, 2012 at 09:43:10AM +, YAMAMOTO Takashi wrote:
> in this particular case, i think that the child does not actually
> need to acquire the lock because the parent always keeps it locked.
> probably some comments and assertion updates are necessary, tho.
Yeah, will fix it that way
hi,
> The question is: do we strip/add the string namespace when
> storing/reading the values in the filesystem.
>
> For native use, I think we do not want to strip, as it is simplier. The
i agree.
> problem arise when mounting a disk from FreeBSD. Here when we ask to
> store "user.foo", we mea
hi,
> On Mon, Feb 13, 2012 at 06:56:00AM +, YAMAMOTO Takashi wrote:
>> > Good catch - I'll defer the release untill the child has done it's
>> > rw_enter().
>>
>> it would deadlock if in the mean time another thread does rw_enter(WRITER)
>> on the lock.
>
> Hmm, but we can't just use the ex
On Mon, Feb 13, 2012 at 06:56:00AM +, YAMAMOTO Takashi wrote:
> > Good catch - I'll defer the release untill the child has done it's
> > rw_enter().
>
> it would deadlock if in the mean time another thread does rw_enter(WRITER)
> on the lock.
Hmm, but we can't just use the existing parent lo
