From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2FC97C33CB6 for ; Thu, 16 Jan 2020 08:55:01 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id E6BDE207E0 for ; Thu, 16 Jan 2020 08:55:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="VZm4MXe3" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E6BDE207E0 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 821F88E0056; Thu, 16 Jan 2020 03:55:00 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 7A9218E003F; Thu, 16 Jan 2020 03:55:00 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 670D08E0056; Thu, 16 Jan 2020 03:55:00 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0083.hostedemail.com [216.40.44.83]) by kanga.kvack.org (Postfix) with ESMTP id 4E9D68E003F for ; Thu, 16 Jan 2020 03:55:00 -0500 (EST) Received: from smtpin08.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with SMTP id F149C5DDB for ; Thu, 16 Jan 2020 08:54:59 +0000 (UTC) X-FDA: 76382887518.08.comb54_82e87032ae209 X-HE-Tag: comb54_82e87032ae209 X-Filterd-Recvd-Size: 3117 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf47.hostedemail.com (Postfix) with ESMTP for ; Thu, 16 Jan 2020 08:54:59 +0000 (UTC) Received: from localhost (static-140-208-78-212.thenetworkfactory.nl [212.78.208.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 279BD2077B; Thu, 16 Jan 2020 08:54:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1579164898; bh=im6PH8G5iv9p2TMDcipnhtQ7gjuFRc6yjB1ZyTlIgTo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=VZm4MXe3srwoo2p6n2vvF0dVJ/eP/E3GehgNvMe3jEncQW1I1w9gYBqfmy9Q7/HcK H83QNZqvIFcBQAvYH6HyMhw4QCgA1QPCqg/o1g/Ka57FSZnGAoQhxjjCdEV2soq7Ra XS623AmUIvi/UKdOQJKHNiJUJU7LxzPigUKvnn4E= Date: Thu, 16 Jan 2020 09:54:55 +0100 From: Greg Kroah-Hartman To: David Hildenbrand Cc: stable@vger.kernel.org, linux-mm@kvack.org, Oscar Salvador , Michal Hocko , "Aneesh Kumar K . V" , Dan Williams , Andrew Morton , Laurent Vivier , Baoquan He Subject: Re: [PATCH for 4.19-stable 00/25] mm/memory_hotplug: backport of pending stable fixes Message-ID: <20200116085455.GA27815@kroah.com> References: <20200115153339.36409-1-david@redhat.com> <20200115153927.GC3881751@kroah.com> <4a09f161-e2f1-b506-f0fd-2d6c4ea1437c@redhat.com> <20200116083407.GB2359@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Jan 16, 2020 at 09:42:51AM +0100, David Hildenbrand wrote: > On 16.01.20 09:34, Greg Kroah-Hartman wrote: > > On Wed, Jan 15, 2020 at 04:54:59PM +0100, David Hildenbrand wrote: > >>> > >>> And why would 4.9 and 4.4 care about them? > >> > >> The crashes can be trigger under 4.9 and 4.4. If we decide that we do > >> not care, then this series can be dropped. > > > > Do we have users of memory hotplug that are somehow stuck at those old > > versions that can not upgrade? Obviously this didn't work previously > > for them, so moving to a modern kernel might be a good reason to get > > this new feature :) > > That's a good point - but usually when you experience a crash it's too > late for you to realize that you have to move to a newer release :) It > used to work before 4.4 IIRC. > > (one case I am concerned with is when memory onlining after memory > hotplug failed (e.g., because the was an OOM event happening > concurrently) - then memory hotunplug will crash your system.) > > But yeah, I am not aware of a report where somebody actually hit any of > these issues on a stable kernel. Ok, let's start with 4.19 and 4.14 for these for now. Should make things easier, right? thanks, greg k-h