From: kernel test robot <lkp@intel.com>
To: Jason Miu <jasonmiu@google.com>, Alexander Graf <graf@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>,
Changyuan Lyu <changyuanl@google.com>,
David Matlack <dmatlack@google.com>,
David Rientjes <rientjes@google.com>,
Jason Gunthorpe <jgg@nvidia.com>, Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH v1 2/3] memblock: Remove KHO notifier usage
Date: Thu, 2 Oct 2025 00:35:48 +0800 [thread overview]
Message-ID: <202510020000.IIPFcxsW-lkp@intel.com> (raw)
In-Reply-To: <20251001011941.1513050-3-jasonmiu@google.com>
Hi Jason,
kernel test robot noticed the following build errors:
[auto build test ERROR on rppt-memblock/for-next]
[also build test ERROR on linus/master v6.17]
[cannot apply to rppt-memblock/fixes akpm-mm/mm-everything next-20250929]
[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/Jason-Miu/kho-Adopt-KHO-radix-tree-data-structures/20251001-092230
base: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock.git for-next
patch link: https://lore.kernel.org/r/20251001011941.1513050-3-jasonmiu%40google.com
patch subject: [PATCH v1 2/3] memblock: Remove KHO notifier usage
config: x86_64-randconfig-003-20251001 (https://download.01.org/0day-ci/archive/20251002/202510020000.IIPFcxsW-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251002/202510020000.IIPFcxsW-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/202510020000.IIPFcxsW-lkp@intel.com/
All errors (new ones prefixed by >>):
>> lib/test_kho.c:59:44: error: too many arguments to function call, expected 2, have 3
59 | err |= kho_add_subtree(ser, KHO_TEST_FDT, folio_address(state->fdt));
| ~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/kexec_handover.h:30:5: note: 'kho_add_subtree' declared here
30 | int kho_add_subtree(const char *name, void *fdt);
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +59 lib/test_kho.c
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 40)
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 41) static int kho_test_notifier(struct notifier_block *self, unsigned long cmd,
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 42) void *v)
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 43) {
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 44) struct kho_test_state *state = &kho_test_state;
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 45) struct kho_serialization *ser = v;
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 46) int err = 0;
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 47)
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 48) switch (cmd) {
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 49) case KEXEC_KHO_ABORT:
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 50) return NOTIFY_DONE;
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 51) case KEXEC_KHO_FINALIZE:
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 52) /* Handled below */
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 53) break;
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 54) default:
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 55) return NOTIFY_BAD;
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 56) }
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 57)
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 58) err |= kho_preserve_folio(state->fdt);
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 @59) err |= kho_add_subtree(ser, KHO_TEST_FDT, folio_address(state->fdt));
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 60)
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 61) return err ? NOTIFY_BAD : NOTIFY_DONE;
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 62) }
b753522bed0b7e Mike Rapoport (Microsoft 2025-07-27 63)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-01 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 1:19 [PATCH v1 0/3] Make KHO Stateless Jason Miu
2025-10-01 1:19 ` [PATCH v1 1/3] kho: Adopt KHO radix tree data structures Jason Miu
2025-10-02 4:29 ` kernel test robot
2025-10-06 14:14 ` Jason Gunthorpe
2025-10-06 17:26 ` Pasha Tatashin
2025-10-06 22:50 ` Jason Gunthorpe
2025-10-09 2:07 ` Jason Miu
2025-10-09 17:52 ` Jason Gunthorpe
2025-10-22 0:59 ` Jason Miu
2025-10-01 1:19 ` [PATCH v1 2/3] memblock: Remove KHO notifier usage Jason Miu
2025-10-01 16:35 ` kernel test robot [this message]
2025-10-01 1:19 ` [PATCH v1 3/3] kho: Remove notifier system infrastructure Jason Miu
2025-10-01 18:07 ` 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=202510020000.IIPFcxsW-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=changyuanl@google.com \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=jgg@nvidia.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
/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