Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp453583img; Fri, 22 Mar 2019 01:25:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqz9jSQgKMpDDWq6ZpNFm4ZxWD9COAtGmA1eo5o4sPMqXKv5Y9pQqPFdKAUDpk/n/8URpKTl X-Received: by 2002:a17:902:8f81:: with SMTP id z1mr8405042plo.265.1553243146041; Fri, 22 Mar 2019 01:25:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553243146; cv=none; d=google.com; s=arc-20160816; b=n4OchS9aihHX8LiAHOy2bcRA9XY6APC6f+TsG4sfUT0bL+/3n9DBs1efdqai4wxyrz 3v4k0/zHbP7CFGRGjrV44noL5RdDsMVctlvF2xMTUKlEHxgdU6Bws982jxQNS3OvNmo5 z+Uc+psJvcye/ZNIcU/9r/d63TyzLT64PSIv3JdSXVC08x+0WH5BjMIt1Dzv9UX8/D4Y MLaT3W9diEc1mbWfkFwnj4D93+/iwelTHSQn073aB0e6plgYam01WTD88q/iP9GkczEq HcTb2VF6LIYrXpXMSvSLWSHEbI3uEtFDLLYL+DjFyc+LLgVJL3moldqulQS0ms0gzNB0 r0YA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=gBzMpH9eoY2j46oXb5oa8zm2zu93w5b+vtsUdolkkbM=; b=MO0mrI8Ilu69DYHoZF2kvctd3bed2usu7s1JhMm5V12mYvUBAnOgwn2LDTPAxeqs4W vd2VQj0jI12/Q/SSeNaRm8SpY7WI2ZunTyw11g4diMMUvyfYeF9NjbVwo5RbPN6iIEeu PpMMR57BFr1neEwOXGMdB5pXD3oDzfYsfBRO/UiyD4xuGbSd2rWPDDgIHjDz2UTVFV0V YLamqVFEpQI6vPrXeJxyI7PVTQvN3Z4NV0MPcuwTMnL2QzONrsY84kY95PstGrNMFxXP GVQ5lKD7Gp09KnCBEYBzAs8yaiWsls3ZHYxkAdE3hIsOcfvKpWLgZCYEN5i0V3voqcLl CJrA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l17si5969815pff.202.2019.03.22.01.25.29; Fri, 22 Mar 2019 01:25:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727766AbfCVIWh (ORCPT + 99 others); Fri, 22 Mar 2019 04:22:37 -0400 Received: from mx2.suse.de ([195.135.220.15]:48120 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727646AbfCVIWh (ORCPT ); Fri, 22 Mar 2019 04:22:37 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id E8A59AEE5; Fri, 22 Mar 2019 08:22:35 +0000 (UTC) Date: Fri, 22 Mar 2019 09:22:35 +0100 From: Michal Hocko To: Souptick Joarder Cc: Qian Cai , Andrew Morton , osalvador@suse.de, anshuman.khandual@arm.com, Linux-MM , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [RESEND PATCH] mm/hotplug: fix notification in offline error path Message-ID: <20190322082235.GA32418@dhcp22.suse.cz> References: <20190320204255.53571-1-cai@lca.pw> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 22-03-19 12:20:12, Souptick Joarder wrote: > On Thu, Mar 21, 2019 at 2:13 AM Qian Cai wrote: > > > > When start_isolate_page_range() returned -EBUSY in __offline_pages(), it > > calls memory_notify(MEM_CANCEL_OFFLINE, &arg) with an uninitialized > > "arg". As the result, it triggers warnings below. Also, it is only > > necessary to notify MEM_CANCEL_OFFLINE after MEM_GOING_OFFLINE. > > For my clarification, if test_pages_in_a_zone() failed in __offline_pages(), > we have the similar scenario as well. If yes, do we need to capture it > in change log ? Yes this is the same situation. We can add a note that the same applies to test_pages_in_a_zone failure path but I do not think it is strictly necessary. Thanks for the note anyway. -- Michal Hocko SUSE Labs