Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752785AbdDDHke (ORCPT ); Tue, 4 Apr 2017 03:40:34 -0400 Received: from mx2.suse.de ([195.135.220.15]:46104 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751094AbdDDHkd (ORCPT ); Tue, 4 Apr 2017 03:40:33 -0400 Date: Tue, 4 Apr 2017 09:40:29 +0200 From: Michal Hocko To: Doug Anderson Cc: Greg KH , arve@android.com, riandrews@android.com, Todd Kjos , devel@driverdev.osuosl.org, "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" Subject: Re: [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read() Message-ID: <20170404074028.GD15132@dhcp22.suse.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 588 Lines: 15 On Mon 03-04-17 11:09:32, Doug Anderson wrote: [...] > Maybe +Michal Hocko would have some opinions of which OOM Reaper > patches would be good for picking into linux stable? I am lacking context here but please note that the OOM reaper patches alone are not sufficient to make the OOM handling lockup free. There were quite some changes in the core OOM killer handling to make this possible. This has been work throughout the last year and it will be really non-trivial to backport to stable trees. So the primary question is what are you trying to achieve? -- Michal Hocko SUSE Labs