[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170913150904.90a37a966a04ea394a2c3d9b@linux-foundation.org>
Date: Wed, 13 Sep 2017 15:09:04 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Sherry Yang <sherryy@...roid.com>
Cc: linux-kernel@...r.kernel.org, tkjos@...gle.com, maco@...gle.com,
arve@...roid.com, gregkh@...uxfoundation.org,
Ingo Molnar <mingo@...nel.org>, Michal Hocko <mhocko@...e.com>,
Vlastimil Babka <vbabka@...e.cz>,
David Rientjes <rientjes@...gle.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andy Lutomirski <luto@...nel.org>,
Oleg Nesterov <oleg@...hat.com>,
Hoeun Ryu <hoeun.ryu@...il.com>,
Christoph Lameter <cl@...ux.com>,
Vegard Nossum <vegard.nossum@...cle.com>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH] mm: Restore mmput_async
On Wed, 13 Sep 2017 17:59:27 -0400 Sherry Yang <sherryy@...roid.com> wrote:
> Restore asynchronous mmput, allowing mmput_async to be called
> from an atomic context in Android binder shrinker callback.
>
> mmput_async was initially introduced in ec8d7c14e
> ("mm, oom_reaper: do not mmput synchronously from the
> oom reaper context"), and was removed in 212925802
> ("mm: oom: let oom_reap_task and exit_mmap run concurrently")
Presumably there's a patch somewhere which adds a call to mmput_async()
into drivers/android/binder.c? Where is that patch?
Powered by blists - more mailing lists