From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754557AbdBGN6B (ORCPT ); Tue, 7 Feb 2017 08:58:01 -0500 Received: from mx2.suse.de ([195.135.220.15]:43904 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753850AbdBGN6A (ORCPT ); Tue, 7 Feb 2017 08:58:00 -0500 Subject: Re: mm: deadlock between get_online_cpus/pcpu_alloc To: Michal Hocko References: <20170206220530.apvuknbagaf2rdlw@techsingularity.net> <20170207084855.GC5065@dhcp22.suse.cz> <20170207094300.cuxfqi35wflk5nr5@techsingularity.net> <2cdef192-1939-d692-1224-8ff7d7ff7203@suse.cz> <20170207102809.awh22urqmfrav5r6@techsingularity.net> <20170207103552.GH5065@dhcp22.suse.cz> <20170207113435.6xthczxt2cx23r4t@techsingularity.net> <20170207114327.GI5065@dhcp22.suse.cz> <20170207123708.GO5065@dhcp22.suse.cz> <0bbc50c4-b18a-a510-ba75-4d7415f15e82@suse.cz> <20170207124835.GP5065@dhcp22.suse.cz> Cc: Mel Gorman , Dmitry Vyukov , Tejun Heo , Christoph Lameter , "linux-mm@kvack.org" , LKML , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , syzkaller , Andrew Morton From: Vlastimil Babka Message-ID: Date: Tue, 7 Feb 2017 14:57:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170207124835.GP5065@dhcp22.suse.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/07/2017 01:48 PM, Michal Hocko wrote: > On Tue 07-02-17 13:43:39, Vlastimil Babka wrote: > [...] >> > Anyway, shouldn't be it sufficient to disable preemption >> > on drain_local_pages_wq? The CPU hotplug callback will not preempt us >> > and so we cannot work on the same cpus, right? >> >> I thought the problem here was that the callback races with the work item >> that has been migrated to a different cpu. Once we are not working on the >> local cpu, disabling preempt/irq's won't help? > > If the worker is racing with the callback than only one of can run on a > _particular_ cpu. So they cannot race. Or am I missing something? Ah I forgot that migrated work item will in fact run on local cpu. So looks like nobody should race with the callback indeed (assuming that when the callback is called, the cpu in question already isn't executing workqueue workers).