From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wj0-f197.google.com (mail-wj0-f197.google.com [209.85.210.197]) by kanga.kvack.org (Postfix) with ESMTP id 8C3746B0033 for ; Tue, 7 Feb 2017 08:58:00 -0500 (EST) Received: by mail-wj0-f197.google.com with SMTP id h7so25729765wjy.6 for ; Tue, 07 Feb 2017 05:58:00 -0800 (PST) Received: from mx2.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id z22si5131262wrc.201.2017.02.07.05.57.59 for (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 07 Feb 2017 05:57:59 -0800 (PST) Subject: Re: mm: deadlock between get_online_cpus/pcpu_alloc 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> From: Vlastimil Babka Message-ID: Date: Tue, 7 Feb 2017 14:57:56 +0100 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: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: Mel Gorman , Dmitry Vyukov , Tejun Heo , Christoph Lameter , "linux-mm@kvack.org" , LKML , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , syzkaller , Andrew Morton 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). -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org