[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1493231242.18659.28.camel@perches.com>
Date: Wed, 26 Apr 2017 11:27:22 -0700
From: Joe Perches <joe@...ches.com>
To: Subhash Jadavani <subhashj@...eaurora.org>,
SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: linux-scsi@...r.kernel.org,
"James E. J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Vinayak Holikatti <vinholikatti@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org, Wolfram Sang <wsa@...-dreams.de>,
linux-scsi-owner@...r.kernel.org
Subject: Re: [PATCH 2/3] scsi: ufs: Delete an error message for a failed
memory allocation in ufshcd_memory_alloc()
On Wed, 2017-04-26 at 10:57 -0700, Subhash Jadavani wrote:
> PS: ufshcd_memory_alloc() also does some DMA coherent memory allocation
> (via dmam_alloc_coherent() APIs) and tries to print out the message on
> allocation failure. Although i don't know "out of memory" messages will
> be printed out by dmam_alloc_coherent() APIs or not. If it does print it
> out then we might want to remove our local memory allocation failure log
> messages.
Basically most everything that has a gfp_t argument does a
dump_stack() on OOM unless __GFP_NOWARN is specified by that gfp_t.
Powered by blists - more mailing lists