From: kernel test robot <lkp@intel.com>
To: xur@google.com, Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Eric Naim <dnaim@cachyos.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Miguel Ojeda <ojeda@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Alice Ryhl <aliceryhl@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Rafael Aquini <aquini@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Stafford Horne <shorne@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Teresa Johnson <tejohnson@google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3] kbuild: distributed build support for Clang ThinLTO
Date: Sun, 25 May 2025 19:14:52 +0800 [thread overview]
Message-ID: <202505251836.qXs81x9F-lkp@intel.com> (raw)
In-Reply-To: <20250521213534.3159514-1-xur@google.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on masahiroy-kbuild/for-next]
[also build test WARNING on masahiroy-kbuild/fixes linus/master v6.15-rc7 next-20250523]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/xur-google-com/kbuild-distributed-build-support-for-Clang-ThinLTO/20250522-053726
base: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git for-next
patch link: https://lore.kernel.org/r/20250521213534.3159514-1-xur%40google.com
patch subject: [PATCH v3] kbuild: distributed build support for Clang ThinLTO
config: arm64-randconfig-r131-20250525 (https://download.01.org/0day-ci/archive/20250525/202505251836.qXs81x9F-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce: (https://download.01.org/0day-ci/archive/20250525/202505251836.qXs81x9F-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/202505251836.qXs81x9F-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/sparse-vmemmap.c:442:21: sparse: sparse: cast to non-scalar
>> mm/sparse-vmemmap.c:442:21: sparse: sparse: cast from non-scalar
mm/sparse-vmemmap.c: note: in included file (through include/linux/pgtable.h, include/linux/mm.h):
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast to non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast from non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast to non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast from non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast to non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast from non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast to non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast from non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast to non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast from non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast to non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast from non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast to non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast from non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast to non-scalar
arch/arm64/include/asm/pgtable.h:339:16: sparse: sparse: cast from non-scalar
vim +442 mm/sparse-vmemmap.c
2045a3b8911b6e Feiyang Chen 2022-10-27 415
2045a3b8911b6e Feiyang Chen 2022-10-27 416 int __meminit vmemmap_populate_hugepages(unsigned long start, unsigned long end,
2045a3b8911b6e Feiyang Chen 2022-10-27 417 int node, struct vmem_altmap *altmap)
2045a3b8911b6e Feiyang Chen 2022-10-27 418 {
2045a3b8911b6e Feiyang Chen 2022-10-27 419 unsigned long addr;
2045a3b8911b6e Feiyang Chen 2022-10-27 420 unsigned long next;
2045a3b8911b6e Feiyang Chen 2022-10-27 421 pgd_t *pgd;
2045a3b8911b6e Feiyang Chen 2022-10-27 422 p4d_t *p4d;
2045a3b8911b6e Feiyang Chen 2022-10-27 423 pud_t *pud;
2045a3b8911b6e Feiyang Chen 2022-10-27 424 pmd_t *pmd;
2045a3b8911b6e Feiyang Chen 2022-10-27 425
2045a3b8911b6e Feiyang Chen 2022-10-27 426 for (addr = start; addr < end; addr = next) {
2045a3b8911b6e Feiyang Chen 2022-10-27 427 next = pmd_addr_end(addr, end);
2045a3b8911b6e Feiyang Chen 2022-10-27 428
2045a3b8911b6e Feiyang Chen 2022-10-27 429 pgd = vmemmap_pgd_populate(addr, node);
2045a3b8911b6e Feiyang Chen 2022-10-27 430 if (!pgd)
2045a3b8911b6e Feiyang Chen 2022-10-27 431 return -ENOMEM;
2045a3b8911b6e Feiyang Chen 2022-10-27 432
2045a3b8911b6e Feiyang Chen 2022-10-27 433 p4d = vmemmap_p4d_populate(pgd, addr, node);
2045a3b8911b6e Feiyang Chen 2022-10-27 434 if (!p4d)
2045a3b8911b6e Feiyang Chen 2022-10-27 435 return -ENOMEM;
2045a3b8911b6e Feiyang Chen 2022-10-27 436
2045a3b8911b6e Feiyang Chen 2022-10-27 437 pud = vmemmap_pud_populate(p4d, addr, node);
2045a3b8911b6e Feiyang Chen 2022-10-27 438 if (!pud)
2045a3b8911b6e Feiyang Chen 2022-10-27 439 return -ENOMEM;
2045a3b8911b6e Feiyang Chen 2022-10-27 440
2045a3b8911b6e Feiyang Chen 2022-10-27 441 pmd = pmd_offset(pud, addr);
2045a3b8911b6e Feiyang Chen 2022-10-27 @442 if (pmd_none(READ_ONCE(*pmd))) {
2045a3b8911b6e Feiyang Chen 2022-10-27 443 void *p;
2045a3b8911b6e Feiyang Chen 2022-10-27 444
2045a3b8911b6e Feiyang Chen 2022-10-27 445 p = vmemmap_alloc_block_buf(PMD_SIZE, node, altmap);
2045a3b8911b6e Feiyang Chen 2022-10-27 446 if (p) {
2045a3b8911b6e Feiyang Chen 2022-10-27 447 vmemmap_set_pmd(pmd, p, node, addr, next);
2045a3b8911b6e Feiyang Chen 2022-10-27 448 continue;
2045a3b8911b6e Feiyang Chen 2022-10-27 449 } else if (altmap) {
2045a3b8911b6e Feiyang Chen 2022-10-27 450 /*
2045a3b8911b6e Feiyang Chen 2022-10-27 451 * No fallback: In any case we care about, the
2045a3b8911b6e Feiyang Chen 2022-10-27 452 * altmap should be reasonably sized and aligned
2045a3b8911b6e Feiyang Chen 2022-10-27 453 * such that vmemmap_alloc_block_buf() will always
2045a3b8911b6e Feiyang Chen 2022-10-27 454 * succeed. For consistency with the PTE case,
2045a3b8911b6e Feiyang Chen 2022-10-27 455 * return an error here as failure could indicate
2045a3b8911b6e Feiyang Chen 2022-10-27 456 * a configuration issue with the size of the altmap.
2045a3b8911b6e Feiyang Chen 2022-10-27 457 */
2045a3b8911b6e Feiyang Chen 2022-10-27 458 return -ENOMEM;
2045a3b8911b6e Feiyang Chen 2022-10-27 459 }
2045a3b8911b6e Feiyang Chen 2022-10-27 460 } else if (vmemmap_check_pmd(pmd, node, addr, next))
2045a3b8911b6e Feiyang Chen 2022-10-27 461 continue;
2045a3b8911b6e Feiyang Chen 2022-10-27 462 if (vmemmap_populate_basepages(addr, next, node, altmap))
2045a3b8911b6e Feiyang Chen 2022-10-27 463 return -ENOMEM;
2045a3b8911b6e Feiyang Chen 2022-10-27 464 }
2045a3b8911b6e Feiyang Chen 2022-10-27 465 return 0;
2045a3b8911b6e Feiyang Chen 2022-10-27 466 }
2045a3b8911b6e Feiyang Chen 2022-10-27 467
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-25 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 21:35 [PATCH v3] kbuild: distributed build support for Clang ThinLTO xur
2025-05-24 18:14 ` Masahiro Yamada
2025-05-27 19:33 ` Rong Xu
2025-05-25 8:58 ` Masahiro Yamada
2025-05-27 19:53 ` Rong Xu
2025-05-25 11:14 ` kernel test robot [this message]
2025-05-26 9:05 ` Masahiro Yamada
2025-05-27 19:57 ` Rong Xu
2025-05-26 13:11 ` Masahiro Yamada
2025-05-27 21:05 ` Rong Xu
2025-05-31 6:48 ` Masahiro Yamada
2025-06-02 22:20 ` Rong Xu
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=202505251836.qXs81x9F-lkp@intel.com \
--to=lkp@intel.com \
--cc=aliceryhl@google.com \
--cc=aquini@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dnaim@cachyos.org \
--cc=justinstitt@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nicolas.schier@linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=shorne@gmail.com \
--cc=tejohnson@google.com \
--cc=tglx@linutronix.de \
--cc=xur@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