lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 8 Feb 2013 16:46:44 -0800 From: Greg KH <gregkh@...uxfoundation.org> To: Joe Perches <joe@...ches.com> Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org, linux-wireless@...r.kernel.org Subject: Re: Other alloc/OOM message question On Fri, Feb 08, 2013 at 04:29:59PM -0800, Joe Perches wrote: > On Fri, 2013-02-08 at 17:45 -0500, David Miller wrote: > > From: Joe Perches <joe@...ches.com> > > Date: Thu, 07 Feb 2013 13:46:27 -0800 > > > alloc failures already get standardized OOM > > > messages and a dump_stack. > > Does anyone know if all the other alloc's like > dma_alloc_coherent, dma_alloc_noncoherent, > pci_alloc_consistent always produce OOM messages > via page_alloc/warn_alloc_failed for all arches? If not, they should, to allow this type of cleanups. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists