From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Abhishek Bapat <abhishekbapat@google.com>,
Suren Baghdasaryan <surenb@google.com>, Hao Ge <hao.ge@linux.dev>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/5] alloc_tag: Introduce IOCTLs to toggle allocation tracepoints
Date: Thu, 5 Nov 2026 17:21:04 -0800 [thread overview]
Message-ID: <20261105172104.339c6f598a65056ed46e56fc@linux-foundation.org> (raw)
In-Reply-To: <202611052344.mDV2DB89-lkp@intel.com>
On Thu, 5 Nov 2026 23:15:33 +0800 kernel test robot <lkp@intel.com> wrote:
> Hi Abhishek,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on bcc036cfa1670a64500f6d857eaa71908b79e3fb]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Abhishek-Bapat/alloc_tag-Add-trace-events-for-tracing-allocations/20261104-190336
> base: bcc036cfa1670a64500f6d857eaa71908b79e3fb
> patch link: https://lore.kernel.org/r/37ae7dca766994d3872fcc65b623a80d5d506369.1793818636.git.abhishekbapat%40google.com
> patch subject: [PATCH v5 2/5] alloc_tag: Introduce IOCTLs to toggle allocation tracepoints
> config: xtensa-randconfig-1001-20261105 (https://download.01.org/0day-ci/archive/20261105/202611052344.mDV2DB89-lkp@intel.com/config)
> compiler: xtensa-linux-gcc (GCC) 8.5.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261105/202611052344.mDV2DB89-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202611052344.mDV2DB89-lkp@intel.com/
>
> All warnings (new ones prefixed by >>, old ones prefixed by <<):
>
> >> WARNING: modpost: vmlinux: section mismatch in reference: alloc_tag_trace_enabled+0x2c (section: .text.unlikely) -> initcall_level_names (section: .init.data)
Thanks.
#syz test
From: Andrew Morton <akpm@linux-foundation.org>
Subject: alloc_tag: force inline the allocation tracing check
Date: Thu, 05 Nov 2026 17:18:09 -0800
alloc_tag_trace_enabled() is declared inline, but the compiler can
still emit an out-of-line copy. Force it inline,
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202611052344.mDV2DB89-lkp@intel.com/
Cc: Abhishek Bapat <abhishekbapat@google.com>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Hao Ge <hao.ge@linux.dev>
---
include/linux/alloc_tag.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/include/linux/alloc_tag.h~alloc_tag-introduce-ioctls-to-toggle-allocation-tracepoints-fix
+++ a/include/linux/alloc_tag.h
@@ -161,7 +161,7 @@ static inline bool alloc_tag_is_traced(c
return !!(atomic_read(&tag->ct.flags) & CODETAG_FLAG_TRACE_ON);
}
-static inline bool alloc_tag_trace_enabled(const struct alloc_tag *tag)
+static __always_inline bool alloc_tag_trace_enabled(const struct alloc_tag *tag)
{
if (static_branch_unlikely(&alloc_tag_trace_key))
return tag && alloc_tag_is_traced(tag);
_
next prev parent reply other threads:[~2026-11-06 1:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 19:03 [PATCH v5 0/5] alloc_tag: Introduce selective tracing for MAP Abhishek Bapat
2026-11-04 19:03 ` [PATCH v5 1/5] alloc_tag: Add trace events for tracing allocations Abhishek Bapat
2026-11-04 19:03 ` [PATCH v5 2/5] alloc_tag: Introduce IOCTLs to toggle allocation tracepoints Abhishek Bapat
2026-11-05 15:15 ` kernel test robot
2026-11-06 1:21 ` Andrew Morton [this message]
2026-11-06 7:54 ` Hao Ge
2026-11-04 19:03 ` [PATCH v5 3/5] alloc_tag: Add a flags field to allocinfo_filter Abhishek Bapat
2026-11-04 19:03 ` [PATCH v5 4/5] alloc_tag: Extend allocinfo_filter to support tracing queries Abhishek Bapat
2026-11-04 19:03 ` [PATCH v5 5/5] alloc_tag: Add a test for trace state toggle and filtering Abhishek Bapat
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=20261105172104.339c6f598a65056ed46e56fc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=abhishekbapat@google.com \
--cc=hao.ge@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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
all inboxes | Powered by JetHome®