# Re: How about just O\_EXEC? (was Re: \[PATCH v5 3/6\] fs: Enable to enforce noexec mounts or file exec through O\_MAYEXEC)

- From: Florian Weimer \<hidden\>
- Date: 2020-05-18 07:27:00 
- List: linux-security-module
- Page: https://ratatoskr.run/linux-security-module/2020/05/180191
- Thread: https://ratatoskr.run/linux-api/2020/05/180191/t.md

```text
* Kees Cook:

> I think I misunderstood what you meant (MickaÃ«l got me sorted out
> now). If O_EXEC is already meant to be "EXEC and _not_ READ nor WRITE",
> then yes, this new flag can't be O_EXEC. I was reading the glibc
> documentation (which treats it as a permission bit flag, not POSIX,
> which treats it as a complete mode description).

I see.  I think this part of the manual is actually very Hurd-specific
(before the O_ACCMODE description).  I'll see if I can make this clearer
in the markup.

Thanks,
Florian

```
