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

David Hildenbrand
2021-09-03T09:45:10Z

On 16.08.21 21:48, David Hildenbrand wrote:
> This series removes all in-tree usage of MAP_DENYWRITE from the kernel
> and removes VM_DENYWRITE. We stopped supporting MAP_DENYWRITE for
> user space applications a while ago because of the chance for DoS.
> The last renaming user is binfmt binary loading during exec and
> legacy library loading via uselib().
>

So, how do we want to continue with this? Pick it up for v5.15? Have it
in -next for a while and eventually pick it up for v5.16?

I think the "remove ETXTBSY completely" and "remove the sanity mapping
check" thingies should be done on top.

--
Thanks,

David / dhildenb