From: "Ho-Ren (Jack) Chuang" <horenchuang@bytedance.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
"Huang, Ying" <ying.huang@intel.com>,
SeongJae Park <sj@kernel.org>
Subject: Re: [External] Re: [akpm-mm:mm-unstable 262/270] vmscan.c:(.text+0x2c90): multiple definition of `mt_find_alloc_memory_type'; kernel/sched/fair.o:fair.c:(.text+0x1db4): first defined here
Date: Mon, 1 Apr 2024 16:03:04 -0700 [thread overview]
Message-ID: <CAKPbEqrQ8bUKt1AmuWenxDGGn1Ht9xRfua_9BO5uquRC6=9Niw@mail.gmail.com> (raw)
In-Reply-To: <CAKPbEqqpXc7K11u087wYFux1ij5PnEhwNYk+EpMyUWFMUSKpCQ@mail.gmail.com>
Hi Andrew and SeongJae,
These compilation errors can be solved by adding `static inline` to
the two complaining functions, the same solution as SeongJae mentioned
earlier.
I've tested on my end as listed below and I will send out a V10 soon
after I check a few more things:
```
$ ./tools/testing/kunit/kunit.py run --build_dir ../kunit.out/
[22:53:24] Configuring KUnit Kernel ...
[22:53:24] Building KUnit Kernel ...
Populating config with:
$ make ARCH=um O=../kunit.out/ olddefconfig
Building with:
$ make ARCH=um O=../kunit.out/ --jobs=8
[22:53:30] Starting KUnit Kernel (1/1)...
[...snip...]
[22:53:37] [FAILED] alloc_size_kmalloc_const_test
[...snip...]
[22:53:37] [FAILED] alloc_size_vmalloc_const_test
[...snip...]
[22:53:37] [FAILED] alloc_size_kvmalloc_const_test
[...snip...]
[22:53:37] [FAILED] alloc_size_devm_kmalloc_const_test
[...snip...]
[22:53:37] Testing complete. Ran 306 tests: passed: 260, failed: 4, skipped: 42
[22:53:37] Failures: fortify.alloc_size_kmalloc_const_test,
fortify.alloc_size_vmalloc_const_test,
fortify.alloc_size_kvmalloc_const_test,
fortify.alloc_size_devm_kmalloc_const_test
[22:53:37] Elapsed time: 13.331s total, 0.003s configuring, 5.837s
building, 7.482s running
```
Btw, I noticed there are 4 failed. Please feel free to let me know if
any caused by my code.
Thanks,
On Mon, Apr 1, 2024 at 11:23 AM Ho-Ren (Jack) Chuang
<horenchuang@bytedance.com> wrote:
>
> Hi Andrew,
>
> Thank you. I'm trying to figure out the problem. Will send a V10 to fix this.
>
> On Mon, Apr 1, 2024 at 11:20 AM Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > OK, thanks. I'll drop
> >
> > Patch series "Improved Memory Tier Creation for CPUless NUMA Nodes", v9.
> >
> > and shall await a v10.
> >
>
>
> --
> Best regards,
> Ho-Ren (Jack) Chuang
> 莊賀任
--
Best regards,
Ho-Ren (Jack) Chuang
莊賀任
prev parent reply other threads:[~2024-04-01 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 12:05 kernel test robot
2024-04-01 18:20 ` Andrew Morton
2024-04-01 18:23 ` [External] " Ho-Ren (Jack) Chuang
2024-04-01 23:03 ` Ho-Ren (Jack) Chuang [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='CAKPbEqrQ8bUKt1AmuWenxDGGn1Ht9xRfua_9BO5uquRC6=9Niw@mail.gmail.com' \
--to=horenchuang@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sj@kernel.org \
--cc=ying.huang@intel.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