linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] kmalloc: Return NULL instead of link failure
Date: Tue, 20 Jan 2009 10:53:26 -0500	[thread overview]
Message-ID: <4975F376.4010506@suse.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 The SLAB kmalloc with a constant value isn't consistent with the other
 implementations because it bails out with __you_cannot_kmalloc_that_much
 rather than returning NULL and properly allowing the caller to fall back
 to vmalloc or take other action. This doesn't happen with a non-constant
 value or with SLOB or SLUB.

 Starting with 2.6.28, I've been seeing build failures on s390x. This is
 due to init_section_page_cgroup trying to allocate 2.5MB when the max
 size for a kmalloc on s390x is 2MB.

 It's failing because the value is constant. The workarounds at the call
 size are ugly and the caller shouldn't have to change behavior depending
 on what the backend of the API is.

 So, this patch eliminates the link failure and returns NULL like the
 other implementations.

Signed-off-by: Jeff Mahoney <jeffm@suse.com>
- ---
 include/linux/slab_def.h |   10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

- --- a/include/linux/slab_def.h
+++ b/include/linux/slab_def.h
@@ -43,10 +43,7 @@ static inline void *kmalloc(size_t size,
 			i++;
 #include <linux/kmalloc_sizes.h>
 #undef CACHE
- -		{
- -			extern void __you_cannot_kmalloc_that_much(void);
- -			__you_cannot_kmalloc_that_much();
- -		}
+		return NULL;
 found:
 #ifdef CONFIG_ZONE_DMA
 		if (flags & GFP_DMA)
@@ -77,10 +74,7 @@ static inline void *kmalloc_node(size_t
 			i++;
 #include <linux/kmalloc_sizes.h>
 #undef CACHE
- -		{
- -			extern void __you_cannot_kmalloc_that_much(void);
- -			__you_cannot_kmalloc_that_much();
- -		}
+		return NULL;
 found:
 #ifdef CONFIG_ZONE_DMA
 		if (flags & GFP_DMA)

- -- 
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkl183YACgkQLPWxlyuTD7IMnQCfbf4NvJuyTustFrdJD/lcl6ub
QQ0AniWOsKCWnBWuLLnm6rM+Atq6LBfd
=/evL
-----END PGP SIGNATURE-----

             reply	other threads:[~2009-01-20 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 15:53 Jeff Mahoney [this message]
2009-01-27 21:37 ` [PATCH] kmalloc: Return NULL instead of link failure Andrew Morton
2009-01-27 21:44   ` Jeff Mahoney
2009-01-27 21:49   ` Pekka Enberg

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=4975F376.4010506@suse.com \
    --to=jeffm@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).