From: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public•gmane.org>
To: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public•gmane.org>
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public•gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
Subject: Re: Other alloc/OOM message question
Date: Fri, 8 Feb 2013 16:46:44 -0800 [thread overview]
Message-ID: <20130209004644.GC31290@kroah.com> (raw)
In-Reply-To: <1360369799.13487.5.camel@joe-AO722>
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-6d6DIl74uiNBDgjK7y7TUQ@public•gmane.org>
> > 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-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-02-09 0:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 21:46 [PATCH] drivers: net: Remove remaining alloc/OOM messages Joe Perches
2013-02-07 22:07 ` Arend van Spriel
2013-02-07 23:29 ` Marc Kleine-Budde
2013-02-08 16:19 ` John W. Linville
2013-02-08 22:45 ` David Miller
2013-02-09 0:29 ` Other alloc/OOM message question Joe Perches
2013-02-09 0:46 ` Greg KH [this message]
[not found] ` <20130209004644.GC31290-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-02-09 21:45 ` [RFC PATCH] dma_alloc_consistent: Remove OOM messages after failure Joe Perches
2013-02-10 7:57 ` [PATCH] drivers: net: Remove remaining alloc/OOM messages Vladimir Kondratiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130209004644.GC31290@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public$(echo .)gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public$(echo .)gmane.org \
--cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public$(echo .)gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox