Bug 54831 - Files always have +x in vfat (2.4.9-6) even with noexec
Files always have +x in vfat (2.4.9-6) even with noexec
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-10-20 09:13 EDT by Carlos Rodrigues
Modified: 2007-04-18 12:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-09-06 22:27:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Carlos Rodrigues 2001-10-20 09:13:26 EDT
Description of Problem:
In vfat filesystems files always appear with execute permissions turned on even when using the noexec option. But with the noexec option files can't be executed (as usual) even if they are showing +x for all.

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:
1. mount a vfat filesystem with the noexec option
2. do a ls in some directory with files

Actual Results:
All files have execute permissions

Expected Results:
Files should't have execute permissions.

Additional Information:
Comment 1 Carlos Rodrigues 2001-11-10 08:19:23 EST
The problem still persists with RedHat 7.2's 2.4.9-13.
Comment 2 Charles Sullivan 2001-11-12 11:55:09 EST
With version 2.4.9-12 at least, the problem appears to be in the
display of permissions.  If I copy a simple bash shell script to
a vfat partition, I can actually execute it if I mount the partition
with the option 'exec' but not with the option 'noexec'.  (In either
case the permission is displayed as executable.)
If I reboot Linux using my previous kernel 2.4.3-12, the execute
permissions are correctly displayed.
Comment 3 Carlos Rodrigues 2002-05-22 12:03:57 EDT
The option "showexec" is a decent workaround (although .exe and .com files 
still appear green).

Note You need to log in before you can comment on or make changes to this bug.