From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753297AbbJSMVc (ORCPT ); Mon, 19 Oct 2015 08:21:32 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:34274 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753042AbbJSMVb (ORCPT ); Mon, 19 Oct 2015 08:21:31 -0400 Date: Mon, 19 Oct 2015 15:21:26 +0300 From: "Kirill A. Shutemov" To: Vladimir Davydov Cc: Andrew Morton , "Kirill A. Shutemov" , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: do not inc NR_PAGETABLE if ptlock_init failed Message-ID: <20151019122126.GA15819@node.shutemov.name> References: <1445256881-5205-1-git-send-email-vdavydov@virtuozzo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1445256881-5205-1-git-send-email-vdavydov@virtuozzo.com> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 19, 2015 at 03:14:41PM +0300, Vladimir Davydov wrote: > If ALLOC_SPLIT_PTLOCKS is defined, ptlock_init may fail, in which case > we shouldn't increment NR_PAGETABLE. > > Since small allocations, such as ptlock, normally do not fail (currently > they can fail if kmemcg is used though), this patch does not really fix > anything and should be considered as a code cleanup. > > Signed-off-by: Vladimir Davydov Acked-by: Kirill A. Shutemov -- Kirill A. Shutemov