From: Minchan Kim <minchan@kernel.org>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
Namhyung Kim <namhyung@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] slub: set PG_slab on all of slab pages
Date: Sun, 4 Mar 2012 19:34:46 +0900 [thread overview]
Message-ID: <20120304103446.GA9267@barrios> (raw)
In-Reply-To: <1330505674-31610-1-git-send-email-namhyung.kim@lge.com>
Hi Namhyung,
On Wed, Feb 29, 2012 at 05:54:34PM +0900, Namhyung Kim wrote:
> Unlike SLAB, SLUB doesn't set PG_slab on tail pages, so if a user would
> call free_pages() incorrectly on a object in a tail page, she will get
>i confused with the undefined result. Setting the flag would help her by
> emitting a warning on bad_page() in such a case.
>
> Reported-by: Sangseok Lee <sangseok.lee@lge.com>
> Signed-off-by: Namhyung Kim <namhyung.kim@lge.com>
I read this thread and I feel the we don't reach right point.
I think it's not a compound page problem.
We can face above problem where we allocates big order page without __GFP_COMP
and free middle page of it.
Fortunately, We can catch such a problem by put_page_testzero in __free_pages
if you enable CONFIG_DEBUG_VM.
Did you tried that with CONFIG_DEBUG_VM?
> ---
> mm/slub.c | 12 ++++++++++--
> 1 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index 33bab2aca882..575baacbec9b 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -1287,6 +1287,7 @@ static struct page *allocate_slab(struct kmem_cache *s, gfp_t flags, int node)
> struct page *page;
> struct kmem_cache_order_objects oo = s->oo;
> gfp_t alloc_gfp;
> + int i;
>
> flags &= gfp_allowed_mask;
>
> @@ -1320,6 +1321,9 @@ static struct page *allocate_slab(struct kmem_cache *s, gfp_t flags, int node)
> if (!page)
> return NULL;
>
> + for (i = 0; i < 1 << oo_order(oo); i++)
> + __SetPageSlab(page + i);
> +
> if (kmemcheck_enabled
> && !(s->flags & (SLAB_NOTRACK | DEBUG_DEFAULT_FLAGS))) {
> int pages = 1 << oo_order(oo);
> @@ -1369,7 +1373,6 @@ static struct page *new_slab(struct kmem_cache *s, gfp_t flags, int node)
>
> inc_slabs_node(s, page_to_nid(page), page->objects);
> page->slab = s;
> - page->flags |= 1 << PG_slab;
>
> start = page_address(page);
>
> @@ -1396,6 +1399,7 @@ static void __free_slab(struct kmem_cache *s, struct page *page)
> {
> int order = compound_order(page);
> int pages = 1 << order;
> + int i;
>
> if (kmem_cache_debug(s)) {
> void *p;
> @@ -1413,7 +1417,11 @@ static void __free_slab(struct kmem_cache *s, struct page *page)
> NR_SLAB_RECLAIMABLE : NR_SLAB_UNRECLAIMABLE,
> -pages);
>
> - __ClearPageSlab(page);
> + for (i = 0; i < pages; i++) {
> + BUG_ON(!PageSlab(page + i));
> + __ClearPageSlab(page + i);
> + }
> +
> reset_page_mapcount(page);
> if (current->reclaim_state)
> current->reclaim_state->reclaimed_slab += pages;
> --
> 1.7.9
>
> --
> 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/ .
> Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-03-04 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 8:54 [PATCH -next] slub: set PG_slab on all of slab pages Namhyung Kim
2012-02-29 15:24 ` Christoph Lameter
2012-03-01 7:30 ` Namhyung Kim
2012-03-01 15:03 ` Christoph Lameter
2012-03-02 7:12 ` Namhyung Kim
2012-03-02 16:13 ` Christoph Lameter
2012-03-04 10:34 ` Minchan Kim [this message]
2012-03-05 8:42 ` Namhyung Kim
2012-03-05 10:59 ` Minchan Kim
2012-03-05 14:48 ` Christoph Lameter
2012-03-06 1:16 ` Minchan Kim
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=20120304103446.GA9267@barrios \
--to=minchan@kernel.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=namhyung.kim@lge.com \
--cc=namhyung@gmail.com \
--cc=penberg@kernel.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).