From: David Howells <dhowells@redhat.com>
To: Leonardo Chiquitto <leonardo.lists@gmail.com>
Cc: dhowells@redhat.com, autofs@linux.kernel.org,
Ian Kent <raven@themaw.net>
Subject: Re: stat -L triggering mount (behavior change starting with 2.6.38-rc1)
Date: Fri, 01 Apr 2011 15:27:25 +0100 [thread overview]
Message-ID: <6929.1301668045@redhat.com> (raw)
In-Reply-To: <AANLkTin0X+F15LxXu8f4SVZEV=twHO9kf7=K+w2xj1eO@mail.gmail.com>
Leonardo Chiquitto <leonardo.lists@gmail.com> wrote:
> open("/data", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
> fcntl(3, F_GETFD) = 0x1 (flags FD_CLOEXEC)
> getdents64(3, /* 3 entries */, 32768) = 72
> lstat("/data/isos", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
> lgetxattr("/data/isos", "security.selinux", 0x62ad60, 255) = -1 EOPNOTSUPP (Operation not supported)
> getxattr("/data/isos", "system.posix_acl_access", 0x0, 0) = -1 EOPNOTSUPP (Operation not supported)
> getdents64(3, /* 0 entries */, 32768) = 0
Yeah, I suspect the getxattr() is the problem. ls calls libacl to get the
Posix ACL of the target file, but that uses the getxattr() which asserts
LOOKUP_FOLLOW during the pathwalk, causing the automount unconditionally:-/
I'm discussing this with the coreutils and acl package maintainers to see if
we can fix it in userspace.
David
next prev parent reply other threads:[~2011-04-01 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 22:53 stat -L triggering mount (behavior change starting with 2.6.38-rc1) Leonardo Chiquitto
2011-04-01 4:27 ` Ian Kent
2011-04-01 4:55 ` Ian Kent
2011-04-01 9:19 ` David Howells
2011-04-01 12:20 ` Leonardo Chiquitto
2011-04-01 14:27 ` David Howells [this message]
2011-08-03 14:16 ` Leonardo Chiquitto
2011-04-01 4:38 ` Ian Kent
2011-04-01 12:13 ` Leonardo Chiquitto
2013-03-26 12:56 ` toto
2013-03-26 20:41 ` Leonardo Chiquitto
2013-03-27 0:13 ` Guillaume Apostoly
2013-03-27 4:06 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 16:19 Leonardo Chiquitto
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=6929.1301668045@redhat.com \
--to=dhowells@redhat.com \
--cc=autofs@linux.kernel.org \
--cc=leonardo.lists@gmail.com \
--cc=raven@themaw.net \
/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.