Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4432239imu; Tue, 29 Jan 2019 01:12:51 -0800 (PST) X-Google-Smtp-Source: ALg8bN7NBhKmNPJ/YPcQSqYOto2PDk0x4kdBLmctJCqq8hsCfJVgJSAC3d58AH4owSZ84w/aqoEM X-Received: by 2002:a63:334a:: with SMTP id z71mr23175469pgz.400.1548753171152; Tue, 29 Jan 2019 01:12:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548753171; cv=none; d=google.com; s=arc-20160816; b=ryhkKmoGTCC2/klHgA3v4xcdkyQgh4ebNu7P1Vu1QvGuqCZ6JOPRVu4dRnbK43UZRW oluMzalS2VWqUaDa8MrNSgfFmlOHDPURv+H5qo4KTN5monBzlVbWxTbIPlpa/yNf6OEi ehR3TUICVaG9CoQFrh48xok8ctaFhzvmorIdFrH0qktK0Y1QoPjU/tCjQqYOuRySr/XL V5wcdqQXhkyj8RomK5ZlGhn50Ktq8roG+oz4cbst7CM9Rah/Iqi5G7q5n2hc9QL5XhND zSVKQ8qLGm7eIn11FWUAoCkEtqAphxbPT9TimRJeyWBzFaQz2KkVsEYLsgdKYdHI3Q30 gVHw== 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=E6few/QoKUbhLkKQPPeCYsGIS/dOtUzP5KGPTeUJWAE=; b=Uqyy2kU3sCDZeYicdrH9pmNd+2FaZkpN9v2D7C3/y5Fl1qJPG2ipzMj8SDeYMUgO54 XH9UXV+P6PEKbdoF7V9ic/SNoYhhn1XTjYxmSA+/sqBKDJvD9zd2A4CdATAHP6d7uQVL Cpc+plLEXWC0j04OasjHfG5DoHMaKY742l26ELeJWKf+JO+gwQbNxsu1NnHO/kWJyefZ UTOoU8LIWiamhzTM+603UUyjs6RiIN+kzmhVQRy6nyAfMjzezvxCz03MsLYxTKrwRUg+ 5e6zCxglwBvOgarhmfEVVn/QL+7DAeZxppWIxA8x3DG6XeChfRX2P37lISW8WRTbw3sA XkPQ== 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 13si11600724pld.398.2019.01.29.01.12.35; Tue, 29 Jan 2019 01:12:51 -0800 (PST) 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 S1727253AbfA2JM1 (ORCPT + 99 others); Tue, 29 Jan 2019 04:12:27 -0500 Received: from mx2.suse.de ([195.135.220.15]:55084 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725298AbfA2JM1 (ORCPT ); Tue, 29 Jan 2019 04:12:27 -0500 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 A5D9BAE89; Tue, 29 Jan 2019 09:12:25 +0000 (UTC) Date: Tue, 29 Jan 2019 10:12:24 +0100 From: Michal Hocko To: Oscar Salvador Cc: Mikhail Zaslonko , Mikhail Gavrilov , Andrew Morton , Pavel Tatashin , schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, gerald.schaefer@de.ibm.com, linux-mm@kvack.org, LKML Subject: Re: [PATCH 1/2] mm, memory_hotplug: is_mem_section_removable do not pass the end of a zone Message-ID: <20190129091224.GG18811@dhcp22.suse.cz> References: <20190128144506.15603-1-mhocko@kernel.org> <20190128144506.15603-2-mhocko@kernel.org> <20190129090605.lenisalq2zxtck3u@d104.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190129090605.lenisalq2zxtck3u@d104.suse.de> 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 Tue 29-01-19 10:06:05, Oscar Salvador wrote: > On Mon, Jan 28, 2019 at 03:45:05PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > Mikhail has reported the following VM_BUG_ON triggered when reading > > sysfs removable state of a memory block: > > page:000003d082008000 is uninitialized and poisoned > > page dumped because: VM_BUG_ON_PAGE(PagePoisoned(p)) > > Call Trace: > > ([<0000000000385b26>] test_pages_in_a_zone+0xde/0x160) > > [<00000000008f15c4>] show_valid_zones+0x5c/0x190 > > [<00000000008cf9c4>] dev_attr_show+0x34/0x70 > > [<0000000000463ad0>] sysfs_kf_seq_show+0xc8/0x148 > > [<00000000003e4194>] seq_read+0x204/0x480 > > [<00000000003b53ea>] __vfs_read+0x32/0x178 > > [<00000000003b55b2>] vfs_read+0x82/0x138 > > [<00000000003b5be2>] ksys_read+0x5a/0xb0 > > [<0000000000b86ba0>] system_call+0xdc/0x2d8 > > Last Breaking-Event-Address: > > [<0000000000385b26>] test_pages_in_a_zone+0xde/0x160 > > Kernel panic - not syncing: Fatal exception: panic_on_oops > > > > The reason is that the memory block spans the zone boundary and we are > > stumbling over an unitialized struct page. Fix this by enforcing zone > > range in is_mem_section_removable so that we never run away from a > > zone. > > Does that mean that the remaining pages(escaping from the current zone) are not tied to > any other zone? Why? Are these pages "holes" or how that came to be? Yes, those pages should be unreachable because they are out of the zone. Reasons might be various. The memory range is not mem section aligned, or cut due to mem parameter etc. -- Michal Hocko SUSE Labs