Re: [PATCH v1 0/7] Remove in-tree usage of MAP_DENYWRITE

J. Bruce Fields
2021-08-18T15:42:22Z

On Fri, Aug 13, 2021 at 05:49:19PM -0700, Andy Lutomirski wrote:
> I’ll bite. How about we attack this in the opposite direction: remove
> the deny write mechanism entirely.

For what it's worth, Windows has open flags that allow denying read or
write opens. They also made their way into the NFSv4 protocol, but
knfsd enforces them only against other NFSv4 clients. Last I checked,
Samba attempted to emulate them using flock (and there's a comment to
that effect on the flock syscall in fs/locks.c). I don't know what Wine
does.

Pavel Shilovsky posted flags adding O_DENY* flags years ago:

https://lwn.net/Articles/581005/

I keep thinking I should look back at those some day but will probably
never get to it.

I've no idea how Windows applications use them, though I'm told it's
common.

--b.