lkml.org 
[lkml]   [2011]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectFilesystem (directory) permissions meaning difference for x86_64 and x86 for 3.1?
Hi,

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.

In both cases the filesystem is tmpfs with support for posix ACLs and
kernel is 3.1.0.


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

Posix ACLs
# file: /tmp/test
# owner: root
# group: root
user::rwx
group::r-x
group:test:--x
mask::r-x
other::---

# file: test/subtest/
# owner: root
# group: root
user::rwx
group::r-x
group:test:rwx
mask::rwx
other::---


When executing as user test (with test as only group), on x86_64 I get
EPERM on chdir(X) where X is any one of the 4 directories above.

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.

The same results are obtained on XFS filesystem.

Any idea what's wrong?

Both test configs attached.


Bruno[unhandled content-type:application/x-bzip][unhandled content-type:application/x-bzip]
\
 
 \ /
  Last update: 2011-11-09 21:53    [W:0.122 / U:0.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site