From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751657AbdJFCCj (ORCPT ); Thu, 5 Oct 2017 22:02:39 -0400 Received: from smtprelay0125.hostedemail.com ([216.40.44.125]:50409 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751423AbdJFCCh (ORCPT ); Thu, 5 Oct 2017 22:02:37 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::::,RULES_HIT:41:355:379:541:599:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1537:1561:1593:1594:1711:1714:1730:1747:1777:1792:2393:2559:2562:2689:2828:3138:3139:3140:3141:3142:3622:3865:3867:3870:3871:3872:4321:5007:8660:10004:10400:10471:10848:11232:11658:11914:12740:12895:13069:13148:13230:13255:13311:13357:13439:13894:14659:14721:21080:21212:21627:30010:30012:30054:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: rose77_33ad729fc8d2d X-Filterd-Recvd-Size: 1550 Message-ID: <1507255353.4434.54.camel@perches.com> Subject: Re: [PATCH 1/2] powerpc/platforms/cell: Delete an error message for a failed memory allocation in three functions From: Joe Perches To: Michal =?ISO-8859-1?Q?Such=E1nek?= , Julia Lawall Cc: Arnd Bergmann , kernel-janitors@vger.kernel.org, LKML , Paul Mackerras , Jeremy Kerr , linuxppc-dev@lists.ozlabs.org, SF Markus Elfring Date: Thu, 05 Oct 2017 19:02:33 -0700 In-Reply-To: <20171005222949.3a288238@kitsune.suse.cz> References: <62146108-5be0-c236-f404-4be122e162ac@users.sourceforge.net> <20171005220210.681f78e8@kitsune.suse.cz> <20171005222949.3a288238@kitsune.suse.cz> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.22.6-1ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2017-10-05 at 22:29 +0200, Michal Suchánek wrote: > I do not expect the kernel to generate a > stack trace every time memory allocation fails. With all the hooks in > the code it is hard to tell, though. All [kv].alloc failures without __GFP_NOWARN call dump_stack()