linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: kent.overstreet@linux.dev, hch@infradead.org, vbabka@suse.cz,
	 pasha.tatashin@soleen.com, souravpanda@google.com,
	keescook@chromium.org,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 1/1] alloc_tag: mark pages reserved during CMA activation as not tagged
Date: Mon, 12 Aug 2024 12:11:29 -0700	[thread overview]
Message-ID: <CAJuCfpFFEa43D2qMkO_DpscYSAjKrvPo7b3hFMtxDrDAmo=fmg@mail.gmail.com> (raw)
In-Reply-To: <20240812184455.86580-1-surenb@google.com>

On Mon, Aug 12, 2024 at 11:44 AM Suren Baghdasaryan <surenb@google.com> wrote:
>
> During CMA activation, pages in CMA area are prepared and then freed
> without being allocated. This triggers warnings when memory allocation
> debug config (CONFIG_MEM_ALLOC_PROFILING_DEBUG) is enabled. Fix this
> by marking these pages not tagged before freeing them.

This should also have:

Fixes: d224eb0287fb "codetag: debug: mark codetags for reserved pages as empty"

>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> ---
>  mm/mm_init.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/mm/mm_init.c b/mm/mm_init.c
> index 75c3bd42799b..ec9324653ad9 100644
> --- a/mm/mm_init.c
> +++ b/mm/mm_init.c
> @@ -2245,6 +2245,16 @@ void __init init_cma_reserved_pageblock(struct page *page)
>
>         set_pageblock_migratetype(page, MIGRATE_CMA);
>         set_page_refcounted(page);
> +
> +       /* pages were reserved and not allocated */
> +       if (mem_alloc_profiling_enabled()) {
> +               union codetag_ref *ref = get_page_tag_ref(page);
> +
> +               if (ref) {
> +                       set_codetag_empty(ref);
> +                       put_page_tag_ref(ref);
> +               }
> +       }
>         __free_pages(page, pageblock_order);
>
>         adjust_managed_page_count(page, pageblock_nr_pages);
>
> base-commit: d74da846046aeec9333e802f5918bd3261fb5509
> --
> 2.46.0.76.ge559c4bf1a-goog
>


  reply	other threads:[~2024-08-12 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 18:44 Suren Baghdasaryan
2024-08-12 19:11 ` Suren Baghdasaryan [this message]
2024-08-12 19:13   ` Suren Baghdasaryan
2024-08-12 19:26     ` Suren Baghdasaryan

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='CAJuCfpFFEa43D2qMkO_DpscYSAjKrvPo7b3hFMtxDrDAmo=fmg@mail.gmail.com' \
    --to=surenb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=keescook@chromium.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=souravpanda@google.com \
    --cc=vbabka@suse.cz \
    /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