From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: kent.overstreet@linux.dev, vbabka@suse.cz,
pasha.tatashin@soleen.com, souravpanda@google.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, surenb@google.com,
kernel test robot <lkp@intel.com>
Subject: [PATCH 1/1] alloc_tag: Export memory allocation profiling symbols used by modules
Date: Thu, 11 Jul 2024 13:46:26 -0700 [thread overview]
Message-ID: <20240711204626.1669138-1-surenb@google.com> (raw)
Export mem_alloc_profiling_key, page_ext_get() and page_ext_set() symbols
as they can be used by modules (mem_alloc_profiling_key is used indirectly
via mem_alloc_profiling_enabled()).
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>
---
lib/alloc_tag.c | 1 +
mm/page_ext.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/lib/alloc_tag.c b/lib/alloc_tag.c
index c347b8b72d78..c01f9f4e92f2 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;
diff --git a/mm/page_ext.c b/mm/page_ext.c
index 95dd8ffeaf81..57a198c70f98 100644
--- a/mm/page_ext.c
+++ b/mm/page_ext.c
@@ -527,6 +527,7 @@ struct page_ext *page_ext_get(const struct page *page)
return page_ext;
}
+EXPORT_SYMBOL(page_ext_get);
/**
* page_ext_put() - Working with page extended information is done.
@@ -545,3 +546,4 @@ void page_ext_put(struct page_ext *page_ext)
rcu_read_unlock();
}
+EXPORT_SYMBOL(page_ext_put);
base-commit: 9d9a2f29aefdadc86e450308ff056017a209c755
--
2.45.2.993.g49e7a77208-goog
next reply other threads:[~2024-07-11 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 20:46 Suren Baghdasaryan [this message]
2024-07-11 21:07 ` [PATCH 1/1] alloc_tag: Export memory allocation profiling symbols used by modules Andrew Morton
2024-07-11 21:38 ` Suren Baghdasaryan
2024-07-12 4:25 ` Christoph Hellwig
2024-07-12 13:27 ` Suren Baghdasaryan
2024-07-17 1:22 ` 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=20240711204626.1669138-1-surenb@google.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.