From: Pekka Enberg <penberg@cs•helsinki.fi>
To: Nick Piggin <npiggin@suse•de>
Cc: Heiko Carstens <heiko.carstens@de•ibm.com>,
Sachin Sant <sachinp@in•ibm.com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-s390@vger•kernel.org
Subject: Re: Next June 29: Boot failure with SLQB on s390
Date: Tue, 30 Jun 2009 12:20:10 +0300 [thread overview]
Message-ID: <1246353610.8014.18.camel@penberg-laptop> (raw)
In-Reply-To: <20090630090631.GB1114@wotan.suse.de>
On Tue, 2009-06-30 at 11:06 +0200, Nick Piggin wrote:
> Finally, if KMALLOC_SHIFT_SLQB_HIGH is larger than 2MB, then kmalloc_index
> could silently run off the end of its precomputed table and return a -1
> index into the kmalloc slab array, which could result in corruption. Extend
> this to allow up to 32MB (to match SLAB), and add a compile-time error in
> the case that the table is exceeded (also like SLAB).
I wonder if SLQB should just do page allocator pass-through for really
big allocations? That way callers don't need to worry about whether
they're running under SLAB/SLUB/SLOB/SQLB.
Pekka
next prev parent reply other threads:[~2009-06-30 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 6:48 linux-next: Tree for June 29 Stephen Rothwell
2009-06-29 9:44 ` Next June 29: Boot failure with SLQB on s390 Sachin Sant
2009-06-29 10:31 ` Heiko Carstens
2009-06-29 10:39 ` Nick Piggin
2009-06-29 11:50 ` Heiko Carstens
2009-06-29 11:58 ` Nick Piggin
2009-06-29 13:09 ` Heiko Carstens
2009-06-29 14:12 ` Heiko Carstens
2009-06-30 7:34 ` Nick Piggin
2009-06-30 9:06 ` Nick Piggin
2009-06-30 9:20 ` Pekka Enberg [this message]
2009-06-30 9:27 ` Nick Piggin
2009-06-30 9:30 ` Pekka Enberg
2009-06-30 10:09 ` Heiko Carstens
2009-06-30 10:29 ` Nick Piggin
2009-06-30 10:57 ` Pekka Enberg
2009-06-30 5:33 ` Sachin Sant
2009-06-30 8:34 ` Nick Piggin
2009-06-30 10:56 ` Sachin Sant
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=1246353610.8014.18.camel@penberg-laptop \
--to=penberg@cs$(echo .)helsinki.fi \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=npiggin@suse$(echo .)de \
--cc=sachinp@in$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/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