public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.11: mount flag noexec still broken for VFAT partition
Date: 10 Oct 2001 18:10:15 -0700	[thread overview]
Message-ID: <9q2rhn$77i$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0110102258290.28429-100000@gulbis.latnet.lv> <20011010151333.G10443@turbolinux.com> <20011011003609.B18573@l-t.ee>

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.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2001-10-11  1:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 20:01 2.4.11: mount flag noexec still broken for VFAT partition Andris Pavenis
2001-10-10 21:13 ` Andreas Dilger
2001-10-10 22:36   ` Marko Kreen
2001-10-11  1:10     ` H. Peter Anvin [this message]
2001-10-11  2:04       ` Marko Kreen
2001-10-11  2:07       ` [RFC] behaviour of stat() variants (was Re: 2.4.11: mount flag noexec still broken for VFAT partition) Alexander Viro
2001-10-11  6:09     ` 2.4.11: mount flag noexec still broken for VFAT partition Andris Pavenis
2001-10-11  8:14       ` linux-2.4.11-dontuse Why? Sergey S. Kostyliov
2001-10-11 10:12         ` Morten Helgesen
2001-10-11 19:18       ` 2.4.11: mount flag noexec still broken for VFAT partition Peter Bornemann

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='9q2rhn$77i$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox