From: Suren Baghdasaryan <surenb@google.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: Sourav Panda <souravpanda@google.com>,
akpm@linux-foundation.org, yuzhao@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
weixugc@google.com
Subject: Re: [PATCH] mm/codetag: fix arg in pgalloc_tag_copy alloc_tag_sub
Date: Tue, 22 Oct 2024 16:04:31 -0700 [thread overview]
Message-ID: <CAJuCfpHpyCMWSpf_+JZgVNoQ5UMHdo9b258aathkou0dgGPung@mail.gmail.com> (raw)
In-Reply-To: <CA+CK2bCnLyEpT-Tr_GGqTzWcNOviE93cyb=WQ09ksYexbzJ7_A@mail.gmail.com>
On Tue, Oct 22, 2024 at 2:03 PM Pasha Tatashin
<pasha.tatashin@soleen.com> wrote:
>
> On Tue, Oct 22, 2024 at 4:56 PM Sourav Panda <souravpanda@google.com> 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 current unit, which is the number of bytes allocated.
> >
> > Fixes: e0a955bf7f61 ("mm/codetag: add pgalloc_tag_copy()")
> > Signed-off-by: Sourav Panda <souravpanda@google.com>
>
> Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Oops... Thanks for the fix!
Acked-by: Suren Baghdasaryan <surenb@google.com>
>
> Thanks,
> Pasha
>
> > ---
> > 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);
> >
> > --
> > 2.47.0.105.g07ac214952-goog
> >
prev parent reply other threads:[~2024-10-22 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 20:56 Sourav Panda
2024-10-22 21:03 ` Pasha Tatashin
2024-10-22 23:04 ` Suren Baghdasaryan [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=CAJuCfpHpyCMWSpf_+JZgVNoQ5UMHdo9b258aathkou0dgGPung@mail.gmail.com \
--to=surenb@google.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=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