linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Christoph Lameter <cl@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	akpm <akpm@linuxfoundation.org>
Subject: Re: [BUG] SLOB's krealloc() seems bust
Date: Wed, 08 Oct 2008 00:15:47 -0500	[thread overview]
Message-ID: <1223442947.13453.462.camel@calx> (raw)
In-Reply-To: <200810081611.30897.nickpiggin@yahoo.com.au>

On Wed, 2008-10-08 at 16:11 +1100, Nick Piggin wrote:
> On Wednesday 08 October 2008 15:54, Nick Piggin wrote:
> > On Wednesday 08 October 2008 15:46, Matt Mackall wrote:
> > > On Wed, 2008-10-08 at 15:22 +1100, Nick Piggin wrote:
> > > > On Wednesday 08 October 2008 10:08, Matt Mackall wrote:
> 
> > > > > diff -r 5e32b09a1b2b mm/slob.c
> > > > > --- a/mm/slob.c	Fri Oct 03 14:04:43 2008 -0500
> > > > > +++ b/mm/slob.c	Tue Oct 07 18:05:15 2008 -0500
> > > > > @@ -514,9 +514,11 @@
> > > > >  		return 0;
> > > > >
> > > > >  	sp = (struct slob_page *)virt_to_page(block);
> > > > > -	if (slob_page(sp))
> > > > > -		return ((slob_t *)block - 1)->units + SLOB_UNIT;
> > > > > -	else
> > > > > +	if (slob_page(sp)) {
> > > > > +		int align = max(ARCH_KMALLOC_MINALIGN, ARCH_SLAB_MINALIGN);
> > > > > +		unsigned int *m = (unsigned int *)(block - align);
> > > > > +		return SLOB_UNITS(*m); /* round up */
> > > > > +	} else
> > > > >  		return sp->page.private;
> > > > >  }
> > > >
> > > > Yes, I came up with nearly the same patch before reading this
> > > >
> > > > --- linux-2.6/mm/slob.c 2008-10-08 14:43:17.000000000 +1100
> > > > +++ suth/mm/slob.c      2008-10-08 15:11:06.000000000 +1100
> > > > @@ -514,9 +514,11 @@ size_t ksize(const void *block)
> > > >                 return 0;
> > > >
> > > >         sp = (struct slob_page *)virt_to_page(block);
> > > > -       if (slob_page(sp))
> > > > -               return (((slob_t *)block - 1)->units - 1) * SLOB_UNIT;
> > > > -       else
> > > > +       if (slob_page(sp)) {
> > > > +               int align = max(ARCH_KMALLOC_MINALIGN,
> > > > ARCH_SLAB_MINALIGN); +               unsigned int *m = (unsigned int
> > > > *)(block - align); +               return *m + align;
> > > > +       } else
> > > >                 return sp->page.private;
> > > >  }
> > > >
> > > > However, mine is lifted directly from kfree, wheras you do something a
> > > > bit different. Hmm, ksize arguably could be used to find the underlying
> > > > allocated slab size in order to use a little bit more than we'd asked
> > > > for. So probably we should really just `return *m` (don't round up or
> > > > add any padding).
> > >
> > > Huh? ksize should report how much space is available in the buffer. If
> > > we request 33 bytes from SLUB and it gives us 64, ksize reports 64. If
> > > we request 33 bytes from SLOB and it gives us 34, we should report 34.
> >
> > Oh.. hmm yeah right, I didn't realise what you were doing there.
> > OK, so your patch looks good to me then (provided it is diffed against
> > the previous one, for Linus).
> 
> OK, no, that's why I got confused. SLOB_UNITS will round you up to the
> next SLOB_UNIT. You'd then have to multiply by SLOB_UNIT to get back to
> bytes.

Damnit, how many ways can we get confused by these little details? I'll
spin a final version and run it against the test harness shortly.

-- 
Mathematics is the supreme nostalgia of our time.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-10-08  5:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 13:57 Peter Zijlstra
2008-10-07 14:07 ` Christoph Lameter
2008-10-07 14:13   ` Peter Zijlstra
2008-10-07 14:26     ` Christoph Lameter
2008-10-07 15:00   ` Matt Mackall
2008-10-07 15:20     ` Christoph Lameter
2008-10-07 15:58       ` Matt Mackall
2008-10-07 16:10     ` Peter Zijlstra
2008-10-07 16:37       ` Linus Torvalds
2008-10-07 16:37       ` Matt Mackall
2008-10-07 16:57         ` Pekka Enberg
2008-10-07 17:13           ` Matt Mackall
2008-10-07 17:31             ` Pekka Enberg
2008-10-07 23:08               ` Matt Mackall
2008-10-08  4:22                 ` Nick Piggin
2008-10-08  4:46                   ` Matt Mackall
2008-10-08  4:54                     ` Nick Piggin
2008-10-08  5:11                       ` Nick Piggin
2008-10-08  5:15                         ` Matt Mackall [this message]
2008-10-08  6:43                           ` Peter Zijlstra
2008-10-08  7:25                             ` Pekka Enberg
2008-10-08  7:37                               ` Peter Zijlstra
2008-10-08  7:39                                 ` Pekka Enberg
2008-10-07 17:57         ` Linus Torvalds
2008-10-07 18:11           ` Peter Zijlstra
2008-10-07 18:18             ` Linus Torvalds
2008-10-08 19:51               ` Matt Mackall

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=1223442947.13453.462.camel@calx \
    --to=mpm@selenic.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linuxfoundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=penberg@cs.helsinki.fi \
    --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