From: Andrew Morton <akpm@linux-foundation.org>
To: Sherry Yang <sherryy@android.com>
Cc: linux-kernel@vger.kernel.org, tkjos@google.com, maco@google.com,
arve@android.com, gregkh@linuxfoundation.org,
Ingo Molnar <mingo@kernel.org>, Michal Hocko <mhocko@suse.com>,
Vlastimil Babka <vbabka@suse.cz>,
David Rientjes <rientjes@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@kernel.org>,
Oleg Nesterov <oleg@redhat.com>, Hoeun Ryu <hoeun.ryu@gmail.com>,
Christoph Lameter <cl@linux.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] mm: Restore mmput_async
Date: Wed, 13 Sep 2017 15:09:04 -0700 [thread overview]
Message-ID: <20170913150904.90a37a966a04ea394a2c3d9b@linux-foundation.org> (raw)
In-Reply-To: <20170913215932.86846-1-sherryy@android.com>
On Wed, 13 Sep 2017 17:59:27 -0400 Sherry Yang <sherryy@android.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?
next prev parent reply other threads:[~2017-09-13 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 22:39 [PATCH] android: binder: Drop lru lock in isolate callback Sherry Yang
2017-09-13 21:59 ` [PATCH] mm: Restore mmput_async Sherry Yang
2017-09-13 22:09 ` Andrew Morton [this message]
2017-09-13 22:44 ` Sherry Yang
2017-09-13 22:57 ` Andrew Morton
2017-09-14 0:08 ` Arve Hjønnevåg
2017-09-14 8:19 ` Michal Hocko
2017-09-14 18:22 ` [PATCH v2] android: binder: Drop lru lock in isolate callback Sherry Yang
2017-09-14 20:12 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170913150904.90a37a966a04ea394a2c3d9b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=arve@android.com \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hoeun.ryu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maco@google.com \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=sherryy@android.com \
--cc=tglx@linutronix.de \
--cc=tkjos@google.com \
--cc=vbabka@suse.cz \
--cc=vegard.nossum@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®