Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2843602imm; Sun, 30 Sep 2018 06:12:14 -0700 (PDT) X-Google-Smtp-Source: ACcGV62ZByKw1DUygmf+h4v2hs18ShhMgxK2kjfofCxR1U30fTSN6/x6BWGcH46UhhwS5eva3HkU X-Received: by 2002:a17:902:a40c:: with SMTP id p12-v6mr7302194plq.165.1538313134047; Sun, 30 Sep 2018 06:12:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538313134; cv=none; d=google.com; s=arc-20160816; b=X1Gv0SxUN50lhcc7UM7mYwRSpgC9npJ49B2Pheof4nff36axqh9D/4Q7C/iKsVmQZH 5EYNfEy9e4DxyPHCgOWYMAlQliP1TLSqFj5rv7FiPz0+JkBjhnFbtWrsr3Px7NegRioJ 6djYB4auiYPVUT7hkNYqZsWN6vNC74Fo2jedX3gTcnIWtUuLIWdD+fAMVj2FvWid5Ovo vk6sAfvPgJrx9nf4OZ0WfjnNBx9NVTZTMfOZgqUN7LZqDg40FxCiZUtsDy8Q6IuLOBvS xarCtWVdWlxm26rFCPY2V3DKgAfIqE6xg5FeDr5QWQxg60hUtObvP15bMcHf09QXFkZy HAfQ== 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:dkim-signature; bh=hDriGazQUFLgqv3w1IgbRO0Yx/XYqVB8Yj6dNq6gxKs=; b=eR6Av5+Oqn3Mu4PPeysl6RR54j754JxuZSd7OjFt/DbXxQ5uPzBLnRL1ZPe2kiZ+zO EGjb0jiePlVAJlQYXEKLcIOwLSwSrWfFTljmjWo0E8K3jvhef418ucMxOSfdEASNZC5C aZJVPCIn2l3ikmBSS9O6kSl/P/mpSVNj7HJuQKV3nU6cSrR5JAOooeRfbSEE66dN44q5 k8vFNI8xirNi/nQFffE8E6lddqFt1X1dFyZk8Ud2mVA6JGDPw4jVHHO0XGs38lmXCQZL oc7o69wbPGWYfqTw53iTRYagWqrN2WurhWfz05VMczLuptSaBeGkhzJUPhmXvLMFWMCN nxbg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=J6lHNB2P; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 207-v6si815697pgb.298.2018.09.30.06.11.05; Sun, 30 Sep 2018 06:12:14 -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; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=J6lHNB2P; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728453AbeI3Tna (ORCPT + 99 others); Sun, 30 Sep 2018 15:43:30 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:49521 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728380AbeI3Tna (ORCPT ); Sun, 30 Sep 2018 15:43:30 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 340A120F1D; Sun, 30 Sep 2018 09:10:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sun, 30 Sep 2018 09:10:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=hDriGazQUFLgqv3w1IgbRO0Yx/XYq VB8Yj6dNq6gxKs=; b=J6lHNB2P4n2sXO/AJXRs45dwrMDqiJ1NKkuO3Skfg45W0 Jg2w5n538nMVFqyQfdxDJDMAxJa4+ycJzhCR0IXfcQ+Ip+vnw7QlCXtnyvrZELaP uIyHOD8u6gex/9nP+vVyBtLRbzx2byzXSeCzoPd0reZLbFqfF/+q+TyTNOZAdlJB a1Gq9n6MDm4S8hvY9MBJ2e0ynMM5FPYIgoq2IlbjQl5HrHyNXXZce791OqSD9M2P 2G54XgAe078nHiOjKqPVLopQ5JQSvHY9Qu09qZCnjMfLgG4QrLFqfsfj/o+jNu0B PLLUE/wR10OcBPnr/f2cev2ay2wFswSOO7bbALQ1A== X-ME-Proxy: X-ME-Sender: Received: from localhost (c-73-221-170-44.hsd1.wa.comcast.net [73.221.170.44]) by mail.messagingengine.com (Postfix) with ESMTPA id C4D1E102A0; Sun, 30 Sep 2018 09:10:27 -0400 (EDT) Date: Sun, 30 Sep 2018 06:10:26 -0700 From: Greg KH To: Matthew Wilcox Cc: zhong jiang , cl@linux.com, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, akpm@linux-foundation.org, mhocko@kernel.org, mgorman@suse.de, vbabka@suse.cz, andrea@kernel.org, kirill@shutemov.name, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [STABLE PATCH] slub: make ->cpu_partial unsigned int Message-ID: <20180930131026.GA25677@kroah.com> References: <1538303301-61784-1-git-send-email-zhongjiang@huawei.com> <20180930125038.GA2533@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180930125038.GA2533@bombadil.infradead.org> 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 Sun, Sep 30, 2018 at 05:50:38AM -0700, Matthew Wilcox wrote: > On Sun, Sep 30, 2018 at 06:28:21PM +0800, zhong jiang wrote: > > From: Alexey Dobriyan > > > > [ Upstream commit e5d9998f3e09359b372a037a6ac55ba235d95d57 ] > > > > /* > > * cpu_partial determined the maximum number of objects > > * kept in the per cpu partial lists of a processor. > > */ > > > > Can't be negative. > > > > I hit a real issue that it will result in a large number of memory leak. > > Becuase Freeing slabs are in interrupt context. So it can trigger this issue. > > put_cpu_partial can be interrupted more than once. > > due to a union struct of lru and pobjects in struct page, when other core handles > > page->lru list, for eaxmple, remove_partial in freeing slab code flow, It will > > result in pobjects being a negative value(0xdead0000). Therefore, a large number > > of slabs will be added to per_cpu partial list. > > > > I had posted the issue to community before. The detailed issue description is as follows. > > > > https://www.spinics.net/lists/kernel/msg2870979.html > > > > After applying the patch, The issue is fixed. So the patch is a effective bugfix. > > It should go into stable. > > > > Link: http://lkml.kernel.org/r/20180305200730.15812-15-adobriyan@gmail.com > > Signed-off-by: Alexey Dobriyan > > Acked-by: Christoph Lameter > > Hang on. Christoph acked the _original_ patch going into upstream. > When he reviewed this patch for _stable_ last week, he asked for more > investigation. Including this patch in stable is misleading. But the original patch has been in upstream for a long time now (it went into 4.17-rc1). If there was a real problem here, whouldn't it have been resolved already? And the patch in mainline has Christoph's ack... thanks, greg k-h