Re: [PATCH] slub: use free_page instead of put_page for freeingkmalloc allocation

[Johannes Weiner]

On Thu, Aug 02, 2012 at 08:51:31PM +0400, Glauber Costa wrote:
> On 08/02/2012 08:42 PM, Johannes Weiner wrote:
> > On Thu, Aug 02, 2012 at 09:06:41AM -0500, Christoph Lameter wrote:
> >> On Thu, 2 Aug 2012, Glauber Costa wrote:
> >>
> >>> diff --git a/mm/slub.c b/mm/slub.c
> >>> index e517d43..9ca4e20 100644
> >>> --- a/mm/slub.c
> >>> +++ b/mm/slub.c
> >>> @@ -3453,7 +3453,7 @@ void kfree(const void *x)
> >>>  	if (unlikely(!PageSlab(page))) {
> >>>  		BUG_ON(!PageCompound(page));
> >>>  		kmemleak_free(x);
> >>> -		put_page(page);
> >>> +		__free_pages(page, compound_order(page));
> >>
> >> Hmmm... put_page would have called put_compound_page(). which would have
> >> called the dtor function. dtor is set to __free_pages() ok which does
> >> mlock checks and verifies that the page is in a proper condition for
> >> freeing. Then it calls free_one_page().
> >>
> >> __free_pages() decrements the refcount and then calls __free_pages_ok().
> >>
> >> So we loose the checking and the dtor stuff with this patch. Guess that is
> >> ok?
> > 
> > The changelog is not correct, however.  People DO get pages underlying
> > slab objects and even free the slab objects before returning the page.
> > See recent fix:
> 
> Well, yes, in the sense that slab objects are page-backed.
> 
> The point is that a user of kmalloc/kfree should not treat a memory area
> as if it were a page, even if it is page-sized.

I whole-heartedly agree.  But it's hard to verify there aren't any
doing that.  And even though it's ugly to do, it's technically
working, no?  No longer supporting it would be a regression.

> If it is just the Changelog you are unhappy about, I can do another
> submission rewording it.

__free_pages still respects the refcount, so I think the Changelog is
not actually appropriate for the change you're making.  You're just
changing what Christoph outlined above, the compound page handling.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/