linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Sourav Panda <souravpanda@google.com>,
	akpm@linux-foundation.org, surenb@google.com, yuzhao@google.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	pasha.tatashin@soleen.com, weixugc@google.com
Subject: Re: [PATCH v2] mm/codetag: fix arg in pgalloc_tag_copy alloc_tag_sub
Date: Wed, 23 Oct 2024 09:49:07 +0530	[thread overview]
Message-ID: <49a7dbae-d382-4b60-b08e-2aaca9eb343f@arm.com> (raw)
In-Reply-To: <20241022232440.334820-1-souravpanda@google.com>


On 10/23/24 04:54, Sourav Panda wrote:
> alloc_tag_sub() takes bytes as opposed to number of pages as argument.
> 
> Currently pgalloc_tag_copy() passes the number of pages. This fix passes
> the correct unit, which is the number of bytes allocated.
> 
> Fixes: e0a955bf7f61 ("mm/codetag: add pgalloc_tag_copy()")
> Signed-off-by: Sourav Panda <souravpanda@google.com>
> Acked-by: Suren Baghdasaryan <surenb@google.com>
> Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> ---
> Changelog:
> Added Acked-by: Suren Baghdasaryan <surenb@google.com>
> Added Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>

Very minor nit.

Just mentioning that the tags have been picked up should suffice.

> Fixed the nit pointed by Wei in the commit message
> 
> v1:
> https://lore.kernel.org/all/20241022205622.133697-1-souravpanda@google.com/
> ---
>  include/linux/mm.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index ecf63d2b0582..2890001c8b97 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -4203,7 +4203,7 @@ static inline void pgalloc_tag_copy(struct folio *new, struct folio *old)
>  	/* Clear the old ref to the original allocation tag. */
>  	clear_page_tag_ref(&old->page);
>  	/* Decrement the counters of the tag on get_new_folio. */
> -	alloc_tag_sub(ref, folio_nr_pages(new));
> +	alloc_tag_sub(ref, folio_size(new));
>  
>  	__alloc_tag_ref_set(ref, tag);
>  

Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>


      reply	other threads:[~2024-10-23  4:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 23:24 Sourav Panda
2024-10-23  4:19 ` Anshuman Khandual [this message]

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=49a7dbae-d382-4b60-b08e-2aaca9eb343f@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=souravpanda@google.com \
    --cc=surenb@google.com \
    --cc=weixugc@google.com \
    --cc=yuzhao@google.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