From mboxrd@z Thu Jan 1 00:00:00 1970 From: William Dauchy Subject: Re: nfsv4 mount with noexec Date: Mon, 3 Jun 2013 01:05:01 +0200 Message-ID: References: <1370206557.46256.12.camel@leira.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: Linux NFS mailing list , "linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" To: "Myklebust, Trond" Return-path: In-Reply-To: <1370206557.46256.12.camel-5lNtUQgoD8Pfa3cDbr2K10B+6BGkLq7r@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Sun, Jun 2, 2013 at 10:56 PM, Myklebust, Trond wrote: > The mount level flags such as 'nosuid', 'nodev' and 'noexec' are > supposed to be enforced by the VFS, and not by the NFS code. The check > is supposedly done in fs/exec.c:open_exec() after the file has been > opened by the filesystem. > > Does 'cat /proc/mounts' actually show the noexec option being applied to > the mountpoint by the kernel? arg I mixed the original mount point and a binded mount point. Sorry for the noise, -- William -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html