From: Nathan Lynch <ntl@pobox.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
mjw <mjw@linux.vnet.ibm.com>, Paul Mackerras <paulus@samba.org>
Subject: Re: Nodes with no memory
Date: Fri, 21 Nov 2008 18:49:56 -0600 [thread overview]
Message-ID: <20081122004956.GT6830@localdomain> (raw)
In-Reply-To: <1227311441.11607.57.camel@nimitz>
Dave Hansen wrote:
> I was handed off a bug report about a blade not booting with a, um
> "newer" kernel.
If you're unable to provide basic information such as the kernel
version then perhaps this isn't the best forum for discussing this. :)
> I'm thinking that we need to at least fix careful_allocation() to oops
> and not return NULL, or check to make sure all it callers check its
> return code.
Well, careful_allocation() in current mainline tries pretty hard to
panic if it can't satisfy the request. Why isn't that happening?
next prev parent reply other threads:[~2008-11-22 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 23:50 Nodes with no memory Dave Hansen
2008-11-22 0:49 ` Nathan Lynch [this message]
2008-11-22 1:17 ` Dave Hansen
2008-11-22 8:58 ` Milton Miller
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=20081122004956.GT6830@localdomain \
--to=ntl@pobox.com \
--cc=dave@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mjw@linux.vnet.ibm.com \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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