From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>, akpm@linux-foundation.org
Cc: kent.overstreet@linux.dev, hch@infradead.org,
pasha.tatashin@soleen.com, souravpanda@google.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/2] alloc_tag: export mem_alloc_profiling_key used by modules
Date: Wed, 17 Jul 2024 11:25:33 +0200 [thread overview]
Message-ID: <875b818a-d6ba-4b79-b1fc-89d6381ed64c@suse.cz> (raw)
In-Reply-To: <20240717011631.2150066-1-surenb@google.com>
On 7/17/24 3:16 AM, Suren Baghdasaryan wrote:
> Export mem_alloc_profiling_key as it is used by modules (indirectly via
> mem_alloc_profiling_enabled()).
>
> Fixes: 22d407b164ff ("lib: add allocation tagging support for memory allocation profiling")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202407080044.DWMC9N9I-lkp@intel.com/
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> lib/alloc_tag.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/alloc_tag.c b/lib/alloc_tag.c
> index 81e5f9a70f22..832f79a32b3e 100644
> --- a/lib/alloc_tag.c
> +++ b/lib/alloc_tag.c
> @@ -15,6 +15,7 @@ EXPORT_SYMBOL(_shared_alloc_tag);
>
> DEFINE_STATIC_KEY_MAYBE(CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT,
> mem_alloc_profiling_key);
> +EXPORT_SYMBOL(mem_alloc_profiling_key);
>
> struct allocinfo_private {
> struct codetag_iterator iter;
>
> base-commit: 0434dbe32053d07d658165be681505120c6b1abc
prev parent reply other threads:[~2024-07-17 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 1:16 Suren Baghdasaryan
2024-07-17 1:16 ` [PATCH 2/2] alloc_tag: outline and export {get|put}_page_tag_ref() " Suren Baghdasaryan
2024-07-17 4:47 ` Christoph Hellwig
2024-07-17 9:30 ` Vlastimil Babka
2024-07-17 16:56 ` Suren Baghdasaryan
2024-07-17 18:24 ` Suren Baghdasaryan
2024-07-17 1:25 ` [PATCH 1/2] alloc_tag: export mem_alloc_profiling_key " Suren Baghdasaryan
2024-07-17 9:25 ` Vlastimil Babka [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=875b818a-d6ba-4b79-b1fc-89d6381ed64c@suse.cz \
--to=vbabka@suse.cz \
--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=lkp@intel.com \
--cc=pasha.tatashin@soleen.com \
--cc=souravpanda@google.com \
--cc=surenb@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