Messages in this thread | | | Subject | Re: FMODE_EXEC or alike? | From | Trond Myklebust <> | Date | Wed, 22 Feb 2006 17:17:33 -0500 |
| |
On Wed, 2006-02-22 at 17:04 -0500, J. Bruce Fields wrote: > What I don't understand is the source of the requirement that > FMODE_WRITE|FMODE_EXEC opens be disallowed. > > The only users of FMODE_EXEC introduced by Oleg's patch use a hardcoded > FMODE_READ|FMODE_EXEC, so it doesn't seem to impose any constraints on > the meaning of FMODE_WRITE|FMODE_EXEC.
I understand FMODE_EXEC to mean that we want to call deny_write_access(). OTOH, FMODE_WRITE is supposed to trigger an automatic call to get_write_access().
Those two calls are mutually exclusive.
Cheers, Trond
- 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/
| |