From: MON KEY <monkey@sandpframing.com>
To: 6297@debbugs.gnu.org
Subject: bug#6297: file-expand-wildcards permission error on top-level mount point
Date: Fri, 28 May 2010 18:30:53 -0400 [thread overview]
Message-ID: <AANLkTinw76DMwHFdks34V3xRDsGuvsaGNEj6LWBiSDoE@mail.gmail.com> (raw)
file-expand-wildcards permission error on top-level mount point
Evaluating (file-expand-wildcards "/*/SOME-DIR/*")
Where the first kleene's target is a mount point e.g.:
"/mnt/SOME-DIR/*"
Signals this error:
(file-error "Opening directory" "permission denied" "/lost+found/")
I'm not sure where the error is getting signalled whether its happening
under the root mount point e.g. "/" or if its occuring under
"/mnt/God-knows-where/..."
On this sytem "lost+found" is the directory that was placed in an ext4
partition for recovery purposes.
It appears that `file-expand-wildcards' gets trounced via
`directory-files' which is signaling an error if the permissions
aren't kosher somewhere.
Shouldn't one of these guys be checking with `file-readable-p' or
`file-attributes' at some such at some point whilst walking the
filesytem?
The error is signalled here too:
(file-expand-wildcards "/*/etc/*.conf")
Whereas this works fine:
(file-expand-wildcards "/etc/*.conf")
which seems odd because in each case (error or not) the permissions
can't be more than root:root i.e. the file-list returnd by the last
form are all root:root.
Surely one shouldn't need to be considering umask/dmask/setuid
etc. just to use this function?
On a GNU Emacs 23.2.1
(i686-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-05-10
--
/s_P\
next reply other threads:[~2010-05-28 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 22:30 MON KEY [this message]
2011-07-03 1:48 ` bug#6297: file-expand-wildcards permission error on top-level mount point Lars Magne Ingebrigtsen
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=AANLkTinw76DMwHFdks34V3xRDsGuvsaGNEj6LWBiSDoE@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=6297@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.