From: kernel test robot <lkp@intel.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>, bpf@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, daniel@iogearbox.net,
andrii@kernel.org, memxor@gmail.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 2/2] bpf: Switch bpf arena to use drm_mm instead of maple_tree
Date: Tue, 5 Nov 2024 13:32:09 +0800 [thread overview]
Message-ID: <202411051357.3XLBnPy3-lkp@intel.com> (raw)
In-Reply-To: <20241101235453.63380-3-alexei.starovoitov@gmail.com>
Hi Alexei,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Alexei-Starovoitov/drm-bpf-Move-drm_mm-c-to-lib-to-be-used-by-bpf-arena/20241102-075645
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20241101235453.63380-3-alexei.starovoitov%40gmail.com
patch subject: [PATCH bpf-next 2/2] bpf: Switch bpf arena to use drm_mm instead of maple_tree
config: i386-randconfig-003-20241104 (https://download.01.org/0day-ci/archive/20241105/202411051357.3XLBnPy3-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241105/202411051357.3XLBnPy3-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/202411051357.3XLBnPy3-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: lib/drm_mm.o: in function `show_leaks':
>> lib/drm_mm.c:135: undefined reference to `__drm_err'
>> ld: lib/drm_mm.c:129: undefined reference to `__drm_err'
vim +135 lib/drm_mm.c
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 117
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 118 static void show_leaks(struct drm_mm *mm)
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 119 {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 120 struct drm_mm_node *node;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 121 char *buf;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 122
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 123 buf = kmalloc(BUFSZ, GFP_KERNEL);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 124 if (!buf)
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 125 return;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 126
2bc98c86517b08 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-12-22 127 list_for_each_entry(node, drm_mm_nodes(mm), node_list) {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 128 if (!node->stack) {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 @129 DRM_ERROR("node [%08llx + %08llx]: unknown owner\n",
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 130 node->start, node->size);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 131 continue;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 132 }
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 133
0f68d45ef41abb drivers/gpu/drm/drm_mm.c Imran Khan 2021-11-08 134 stack_depot_snprint(node->stack, buf, BUFSZ, 0);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 @135 DRM_ERROR("node [%08llx + %08llx]: inserted at\n%s",
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 136 node->start, node->size, buf);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 137 }
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 138
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 139 kfree(buf);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 140 }
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 141
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-05 5:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 23:54 [PATCH bpf-next 0/2] drm, bpf: User drm_mm in bpf Alexei Starovoitov
2024-11-01 23:54 ` [PATCH bpf-next 1/2] drm, bpf: Move drm_mm.c to lib to be used by bpf arena Alexei Starovoitov
2024-11-03 20:03 ` Kumar Kartikeya Dwivedi
2024-11-01 23:54 ` [PATCH bpf-next 2/2] bpf: Switch bpf arena to use drm_mm instead of maple_tree Alexei Starovoitov
2024-11-03 20:04 ` Kumar Kartikeya Dwivedi
2024-11-05 5:32 ` kernel test robot [this message]
2024-11-05 15:58 ` kernel test robot
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=202411051357.3XLBnPy3-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-team@fb.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=memxor@gmail.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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