Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1720634 > unrolled thread

Re: scsi: ufs: Delete an error message for a failed memory allocation in ufshcd_memory_alloc()

Started bySF Markus Elfring <elfring@users.sourceforge.net>
First post2017-08-26 13:20 +0200
Last post2017-08-26 13:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: scsi: ufs: Delete an error message for a failed memory allocation  in ufshcd_memory_alloc() SF Markus Elfring <elfring@users.sourceforge.net> - 2017-08-26 13:20 +0200

#1720634 — Re: scsi: ufs: Delete an error message for a failed memory allocation in ufshcd_memory_alloc()

FromSF Markus Elfring <elfring@users.sourceforge.net>
Date2017-08-26 13:20 +0200
SubjectRe: scsi: ufs: Delete an error message for a failed memory allocation in ufshcd_memory_alloc()
Message-ID<uiHia-ul-21@gated-at.bofh.it>
>> 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.

How do you think about to continue the clarification for this aspect
of the involved programming interfaces?

Regards,
Markus

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web