Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754173Ab3FJXk1 (ORCPT ); Mon, 10 Jun 2013 19:40:27 -0400 Received: from a194-210.smtp-out.amazonses.com ([199.255.194.210]:24624 "EHLO a194-210.smtp-out.amazonses.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753398Ab3FJXkG (ORCPT ); Mon, 10 Jun 2013 19:40:06 -0400 Date: Mon, 10 Jun 2013 23:40:05 +0000 From: Christoph Lameter To: Sasha Levin cc: Pekka Enberg , "linux-mm@kvack.org" , Andrew Morton , LKML Subject: Re: [PATCH] slab: prevent warnings when allocating with __GFP_NOWARN In-Reply-To: <51B62F6B.8040308@oracle.com> Message-ID: <0000013f3075f90d-735942a8-b4b8-413f-a09e-57d1de0c4974-000000@email.amazonses.com> References: <1370891880-2644-1-git-send-email-sasha.levin@oracle.com> <51B62F6B.8040308@oracle.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SES-Outgoing: 199.255.194.210 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1198 Lines: 25 On Mon, 10 Jun 2013, Sasha Levin wrote: > [ 1691.807621] Call Trace: > [ 1691.809473] [] dump_stack+0x4e/0x82 > [ 1691.812783] [] warn_slowpath_common+0x82/0xb0 > [ 1691.817011] [] warn_slowpath_null+0x15/0x20 > [ 1691.819936] [] kmalloc_slab+0x2f/0xb0 > [ 1691.824942] [] __kmalloc+0x24/0x4b0 > [ 1691.827285] [] ? security_capable+0x13/0x20 > [ 1691.829405] [] ? pipe_fcntl+0x107/0x210 > [ 1691.831827] [] pipe_fcntl+0x107/0x210 > [ 1691.833651] [] ? fget_raw_light+0x130/0x3f0 > [ 1691.835343] [] SyS_fcntl+0x60b/0x6a0 > [ 1691.837008] [] tracesys+0xe1/0xe6 > > The caller specifically sets __GFP_NOWARN presumably to avoid this warning on > slub but I'm not sure if there's any other reason. There must be another reason. Lets fix this. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/