linux-kernel - Re: [PATCH v3] android: binder: use VM

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: <CADAEsF-PwG5fNhMUpLFHmQzx7u93K9VJVQGQv5fc2CAPuvg4mg@mail.gmail.com>
Date:   Wed, 24 Jan 2018 13:24:47 +0800
From:   Ganesh Mahendran <opensource.ganesh@...il.com>
To:     Arve Hjønnevåg <arve@...roid.com>
Cc:     Todd Kjos <tkjos@...gle.com>, Greg KH <gregkh@...uxfoundation.org>,
        Martijn Coenen <maco@...roid.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] android: binder: use VM_ALLOC to get vm area

Hi, Arve:

2018-01-23 2:55 GMT+08:00 Arve Hjønnevåg <arve@...roid.com>:
> On Mon, Jan 22, 2018 at 9:02 AM, Todd Kjos <tkjos@...gle.com> wrote:
>> On Mon, Jan 22, 2018 at 7:54 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
>>> On Wed, Jan 10, 2018 at 10:49:05AM +0800, Ganesh Mahendran wrote:
>>>> VM_IOREMAP is used to access hardware through a mechanism called
>>>> I/O mapped memory. Android binder is a IPC machanism which will
>>>> not access I/O memory.
>>>>
>>>> And VM_IOREMAP has alignment requiement which may not needed in
>>>> binder.
>>>>     __get_vm_area_node()
>>>>     {
>>>>     ...
>>>>         if (flags & VM_IOREMAP)
>>>>             align = 1ul << clamp_t(int, fls_long(size),
>>>>                PAGE_SHIFT, IOREMAP_MAX_ORDER);
>>>>     ...
>>>>     }
>>>>
>>>> This patch will save some kernel vm area, especially for 32bit os.
>>>>
>>>> In 32bit OS, kernel vm area is only 240MB. We may got below
>>>> error when launching a app:
>>>>
>>>> <3>[ 4482.440053] binder_alloc: binder_alloc_mmap_handler: 15728 8ce67000-8cf65000 get_vm_area failed -12
>>>> <3>[ 4483.218817] binder_alloc: binder_alloc_mmap_handler: 15745 8ce67000-8cf65000 get_vm_area failed -12
>>>>
>>>> Signed-off-by: Ganesh Mahendran <opensource.ganesh@...il.com>
>>>> ----
>>>> V3: update comments
>>>> V2: update comments
>>>> ---
>>>>  drivers/android/binder_alloc.c | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> Martijn and Todd, any objections to this patch?
>>
>> Looks fine to me. Arve, do you remember the rationale for using VM_IOREMAP?
>>
>
> I don't remember for sure, but I think it used alloc_vm_area at some
> point, and that uses VM_IOREMAP.

Yes, in alloc_vm_area(), it uses VM_IOREMAP flag.

In binder, the ~1MB vm area is cut into binder_buffer which is not
even page aligned.
So for binder IPC, there is no need to align vm area(512KB now).
For 64 bit OS, the vm area is very big, but for 32 bit OS, default vm
area is only 240.
The vm area will soon be exhausted, then no app can be launched.

Thanks.

>
> --
> Arve Hjønnevåg