linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Hui Zhu <zhuhui@xiaomi.com>
Cc: minchan@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, teawater@gmail.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] zsmalloc: fix obj_to_head use page_private(page) as value but not pointer
Date: Tue, 6 Oct 2015 19:59:03 +0900	[thread overview]
Message-ID: <20151006105903.GA8462@swordfish> (raw)
In-Reply-To: <1444033381-5726-1-git-send-email-zhuhui@xiaomi.com>

On (10/05/15 16:23), Hui Zhu wrote:
> In function obj_malloc:
> 	if (!class->huge)
> 		/* record handle in the header of allocated chunk */
> 		link->handle = handle;
> 	else
> 		/* record handle in first_page->private */
> 		set_page_private(first_page, handle);
> The huge's page save handle to private directly.
> 
> But in obj_to_head:
> 	if (class->huge) {
> 		VM_BUG_ON(!is_first_page(page));
> 		return page_private(page);
> 	} else
> 		return *(unsigned long *)obj;
> It is used as a pointer.
> 

um...
obj_to_head() is not for obj_malloc(), but for record_obj() that follows.
handle is a `void *' returned from alloc_handle()->kmem_cache_alloc(), and
casted to 'unsigned long'.

we store obj as:

static void record_obj(unsigned long handle, unsigned long obj)
{
	*(unsigned long *)handle = obj;
}

regardless `class->huge'.


and retrieve it as  `*(unsigned long *)foo', which is either
	`*(unsigned long *)page_private(page)'
or
	`*(unsigned long *)obj'

'return p' and `return *p' do slightly different things for pointers.


am I missing something?

	-ss

> So change obj_to_head use page_private(page) as value but not pointer
> in obj_to_head.
> 
> Signed-off-by: Hui Zhu <zhuhui@xiaomi.com>
> ---
>  mm/zsmalloc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
> index f135b1b..e881d4f 100644
> --- a/mm/zsmalloc.c
> +++ b/mm/zsmalloc.c
> @@ -824,7 +824,7 @@ static unsigned long obj_to_head(struct size_class *class, struct page *page,
>  {
>  	if (class->huge) {
>  		VM_BUG_ON(!is_first_page(page));
> -		return *(unsigned long *)page_private(page);
> +		return page_private(page);
>  	} else
>  		return *(unsigned long *)obj;
>  }
> -- 
> 1.9.1
> 
> --
> 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>
> 

--
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:[~2015-10-06 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05  8:23 Hui Zhu
2015-10-06 10:59 ` Sergey Senozhatsky [this message]
2015-10-06 13:54 ` Minchan Kim
2015-10-07  4:44   ` Hui Zhu
2015-10-07  4:45   ` [PATCH v2] " Hui Zhu

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=20151006105903.GA8462@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=teawater@gmail.com \
    --cc=zhuhui@xiaomi.com \
    /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