From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruno =?UTF-8?B?UHLDqW1vbnQ=?= <bonbons@linux-vserver.org>
Subject: Re: [resolved] Filesystem (directory) permissions meaning
 difference for x86_64 and x86 for 3.1?
Date: Sun, 13 Nov 2011 12:11:05 +0100
Message-ID: <20111113121105.1092d733@neptune.home>
References: <20111109215125.7c1c3d3a@neptune.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: Al Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
To: unlisted-recipients:; (no To-header on input)
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20111109215125.7c1c3d3a@neptune.home>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Wed, 09 November 2011 Bruno Pr=C3=A9mont wrote:
> On a x86_64 system I'm getting permission denied when trying to chdir=
()
> into a directory where I have only 'x' permissions (be it with unix
> permissions or with posix ACLs).
> For the same layout of directory I can successfully chdir() on x86 as=
 I
> can with older kernels of 2.6 series.
>=20
> In both cases the filesystem is tmpfs with support for posix ACLs and
> kernel is 3.1.0.
>=20
>=20
> Directory layout:
> drwx--x---  3 root test   60 Nov  9 21:14 /tmp/btest
> drwxrwx---  2 root test   40 Nov  9 21:14 /tmp/btest/subtest
> drwxr-x---+ 3 root root   60 Nov  9 21:10 /tmp/test
> drwxrwx---+ 2 root root   40 Nov  9 21:10 /tmp/test/subtest
>=20
> Posix ACLs
> # file: /tmp/test
> # owner: root
> # group: root
> user::rwx
> group::r-x
> group:test:--x
> mask::r-x
> other::---
>=20
> # file: test/subtest/
> # owner: root
> # group: root
> user::rwx
> group::r-x
> group:test:rwx
> mask::rwx
> other::---
>=20
>=20
> When executing as user test (with test as only group), on x86_64 I ge=
t
> EPERM on chdir(X) where X is any one of the 4 directories above.
>=20
> On x86 I can chdir() into the directory without issue (as expected),
> and when in /tmp/test (or /tmp/btest) I get EPERM when trying to list
> contents - expected as well. Under subtest I can list content.
>=20
> The same results are obtained on XFS filesystem.
>=20
> Any idea what's wrong?

The issue was two entries in /etc/group for the same group name but wit=
h
two distinct GIDs :/
This explains why I could not reproduce on a different system!

Bruno