[bug-notifications] [findutils 0004682]: -executable option not working

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4682 
====================================================================== 
Reported By:                flod
Assigned To:                
====================================================================== 
Project:                    findutils
Issue ID:                   4682
Category:                   regular use
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2011-02-01 22:52 CET
Last Modified:              2011-05-26 14:01 CEST
====================================================================== 
Summary:                    -executable option not working
Description: 
The "-executable" option is meant to select executable files and searchable
directories.
The option does not work with
4.4.2,REV=2009.06.08
as expected.
I cross-checked the results I hoped for under my Linux installation.

The man page says that the difference between -perm and -executable is
that the latter takes more complex things into account like acls.
So the option would be useful but does not work as expected.



====================================================================== 

---------------------------------------------------------------------- 
 (0009083) flod (reporter) - 2011-05-26 14:01
 https://www.opencsw.org/mantis/view.php?id=4682#c9083 
---------------------------------------------------------------------- 
Okay, thank you for explaining that issue. I read the man page in the first
place but never expected that the syscall could be the source.

>From access(2):
     If any access permissions are to be checked,  each  will  be
     checked  individually, as described in intro(2). If the pro-
     cess has appropriate privileges, an implementation may indi-
     cate  success for X_OK even if none of the execute file per-
     mission bits are set.

I am not sure what appropriate privileges here mean (file_dac_execute?).
I observed the strang behaviour only as root user, maybe root has some
privileges (all) in the context of access().

Please close.