Messages in this thread |  | | Date | Thu, 11 Oct 2001 04:04:25 +0200 | From | Marko Kreen <> | Subject | Re: 2.4.11: mount flag noexec still broken for VFAT partition |
| |
On Wed, Oct 10, 2001 at 06:10:15PM -0700, H. Peter Anvin wrote: > Followup to: <20011011003609.B18573@l-t.ee> > By author: Marko Kreen <marko@l-t.ee> > In newsgroup: linux.dev.kernel > > > > Um. 'noexec' does not touch flags, it only disallows exec'ing > > on particular mountpoint. > > > > It does on FAT filesystems (except UMSDOS), since they don't have real > flags. Files and directories have syntesized attributes of > (0777 & ~umask); noexec is supposed to modify that to (0666 & ~umask) > for files but not directories. > > That has been the Linux behaviour since the 0.x days.
Eh. Seems my brain has managed to filter that out thus far. Probably as "uninteresting" is the only thing I can say :)
What is interesting is that in current vfat I can toggle +x bit on and off with chmod. So it seems like VFS does not consult with fs anymore about bits. But you know that already.
Oh well...
-- marko
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |