From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: Checking error messages for failed memory allocations Date: Wed, 26 Apr 2017 12:05:49 -0700 Message-ID: <1493233549.18659.33.camel@perches.com> References: <75622f45-f46c-e52f-2b9e-6ff5ce32184a@users.sourceforge.net> <3d355c13-159a-2570-9ead-af93ad95c210@users.sourceforge.net> <019b6365c15b0764c156d6453648f7a2@codeaurora.org> <1493231242.18659.28.camel@perches.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Return-path: Received: from smtprelay0105.hostedemail.com ([216.40.44.105]:46785 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753855AbdDZTFx (ORCPT ); Wed, 26 Apr 2017 15:05:53 -0400 In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: SF Markus Elfring Cc: Subhash Jadavani , linux-scsi@vger.kernel.org, "James E. J. Bottomley" , "Martin K. Petersen" , Vinayak Holikatti , LKML , kernel-janitors@vger.kernel.org, Wolfram Sang , linux-scsi-owner@vger.kernel.org On Wed, 2017-04-26 at 20:50 +0200, SF Markus Elfring wrote: > > Basically most everything that has a gfp_t argument does a > > dump_stack() on OOM unless __GFP_NOWARN is specified by that gfp_t. > > How do you think about to improve any programming interface documentation > around such a function property? Feel free to submit documentation patches. > Are there any special checks needed for function implementations > which can pass the flag “__GFP_NOWARN”? No.