public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: David Howells <dhowells@redhat.com>,
	Christoph Lameter <clameter@sgi.com>,
	LKML <linux-kernel@vger.kernel.org>,
	cooloney@kernel.org, akpm@linux-foundation.org, mpm@selenic.com
Subject: Re: [PATCH] nommu: fix kobjsize() for SLOB and SLUB
Date: Sun, 1 Jun 2008 17:22:49 +0900	[thread overview]
Message-ID: <20080601082249.GB25429@linux-sh.org> (raw)
In-Reply-To: <484256AA.3000709@cs.helsinki.fi>

On Sun, Jun 01, 2008 at 10:58:34AM +0300, Pekka Enberg wrote:
> Paul Mundt wrote:
> >Not until the page->index bits are killed, otherwise you aren't fixing
> >anything. SLOB on nommu with those page->index tests will automatically
> >oops today, before or after your patches. Until that's resolved, there's
> >no point in pretending like kobjsize() has been "fixed". As no one has
> >come up with a valid reason for those tests existing in the first place,
> >simply having your patches and killing the BUG_ON()'s seems ok.
> 
> Sorry if I'm starting to sound like a broken record, but can you explain 
> why removing the ->index bits are safe? I mean, if removing them is 
> really okay, that means we don't hit that code path with SLAB at all?
> 
I thought I already had several times, but I'll attempt to summarize again..

I would expect the only reason those BUG_ON()'s haven't been triggered in
the non-SLOB case is due to the fact PageSlab() takes a different path
out.

The page->index bits look like they are being used for determining
compound order, which is _completely_ bogus, and only happens to "work"
in a few cases. Christoph and I have repeatedly asked for someone to
explain what the hell those tests are there for, as right now they not
only look completely bogus, but they also stop us from booting on SLOB.
So far no one has provided any input on why those page->index BUG_ON()'s
have any right to exist.

So while having 2 out of 3 SLAB allocators in a bootable state might seem
like progress, I'd rather see kobjsize() fixed correctly. Even my initial
patches worked for all 3.

If no one can speak up to defend those bits, they should be killed off
before 2.6.26. Whether this is done in combination with your patch or
Christoph's patch or whatever else doesn't matter.

  parent reply	other threads:[~2008-06-01  8:25 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0805281646470.27125@sbz-30.cs.Helsinki.FI>
     [not found] ` <20080528153648.GA27783@linux-sh.org>
2008-05-28 20:03   ` [PATCH] nommu: fix kobjsize() for SLOB and SLUB Pekka Enberg
2008-05-28 20:25     ` Christoph Lameter
2008-05-28 20:25       ` Pekka Enberg
2008-05-28 20:29         ` Christoph Lameter
2008-05-29 13:08           ` David Howells
2008-05-29 13:21             ` Pekka J Enberg
2008-05-29 21:12               ` Paul Mundt
2008-06-01  7:58                 ` Pekka Enberg
2008-06-01  8:22                   ` Pekka J Enberg
2008-06-01  8:24                     ` Paul Mundt
2008-06-01  8:36                       ` Pekka J Enberg
2008-06-01  9:13                       ` Pekka J Enberg
2008-06-01 10:24                         ` Paul Mundt
2008-06-01 10:29                           ` Pekka Enberg
2008-06-01 11:21                             ` Paul Mundt
2008-06-01 11:30                               ` Pekka J Enberg
2008-06-02  5:59                                 ` Paul Mundt
2008-06-02  6:32                                   ` Pekka Enberg
2008-06-02  6:50                                     ` Paul Mundt
2008-06-02  6:58                                       ` Pekka Enberg
2008-06-02  7:01                                         ` Paul Mundt
2008-06-01  8:22                   ` Paul Mundt [this message]
2008-05-29 15:00             ` Christoph Lameter
2008-05-22 16:09 Pekka J Enberg
2008-05-22 16:48 ` Christoph Lameter
2008-05-22 23:40 ` Paul Mundt
2008-05-22 23:45   ` Christoph Lameter
2008-05-22 23:50     ` Paul Mundt
2008-05-23  0:04       ` Christoph Lameter
2008-05-28 13:12 ` David Howells
2008-05-28 13:17   ` Pekka J Enberg
2008-05-28 13:40     ` David Howells
2008-05-28 14:09   ` David Howells
2008-05-28 17:26     ` Christoph Lameter
2008-05-28 17:38       ` David Howells
2008-05-28 20:35         ` Mike Frysinger
2008-05-29 13:03           ` David Howells
2008-05-29 20:25             ` Mike Frysinger
2008-05-29 20:30               ` Christoph Lameter
2008-05-29 20:51                 ` Mike Frysinger
2008-05-29 21:29                   ` Christoph Lameter
2008-05-30  4:18                     ` Mike Frysinger
2008-05-28 14:27   ` David Howells

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=20080601082249.GB25429@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=cooloney@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=penberg@cs.helsinki.fi \
    /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