linux-kernel - Re: [PATCH] mm: mmap: Merge vma after call

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200713202035.55ea84d08a1c39423603f592@linux-foundation.org>
Date:   Mon, 13 Jul 2020 20:20:35 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     linmiaohe <linmiaohe@...wei.com>
Cc:     <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: mmap: Merge vma after call_mmap() if possible

On Tue, 14 Jul 2020 11:07:44 +0800 linmiaohe <linmiaohe@...wei.com> wrote:

> The vm_flags may be changed after call_mmap() because drivers may set some
> flags for their own purpose. As a result, we failed to merge the adjacent
> vma due to the different vm_flags as userspace can't pass in the same one.
> Try to merge vma after call_mmap() to fix this issue.

Which drivers do this?