From: kernel test robot <lkp@intel.com>
To: Lukas Hruska <lhruska@suse.cz>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 1/4 v1] crash/vmcore: VMCOREINFO creation from non-kdump kernel
Date: Sat, 11 Nov 2023 07:26:07 +0800 [thread overview]
Message-ID: <202311110746.PACzMVRq-lkp@intel.com> (raw)
In-Reply-To: <20231110150057.15717-2-lhruska@suse.cz>
Hi Lukas,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on tip/x86/mm linus/master v6.6 next-20231110]
[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/Lukas-Hruska/crash-vmcore-VMCOREINFO-creation-from-non-kdump-kernel/20231111-022332
base: tip/x86/core
patch link: https://lore.kernel.org/r/20231110150057.15717-2-lhruska%40suse.cz
patch subject: [RFC PATCH 1/4 v1] crash/vmcore: VMCOREINFO creation from non-kdump kernel
config: loongarch-randconfig-002-20231111 (https://download.01.org/0day-ci/archive/20231111/202311110746.PACzMVRq-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231111/202311110746.PACzMVRq-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/202311110746.PACzMVRq-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/crash_dump.c: In function 'elfcorehdr_read_notes':
>> kernel/crash_dump.c:77:25: error: implicit declaration of function 'cc_platform_has' [-Werror=implicit-function-declaration]
77 | cc_platform_has(CC_ATTR_MEM_ENCRYPT));
| ^~~~~~~~~~~~~~~
>> kernel/crash_dump.c:77:41: error: 'CC_ATTR_MEM_ENCRYPT' undeclared (first use in this function)
77 | cc_platform_has(CC_ATTR_MEM_ENCRYPT));
| ^~~~~~~~~~~~~~~~~~~
kernel/crash_dump.c:77:41: note: each undeclared identifier is reported only once for each function it appears in
kernel/crash_dump.c:78:1: warning: control reaches end of non-void function [-Wreturn-type]
78 | }
| ^
cc1: some warnings being treated as errors
vim +/cc_platform_has +77 kernel/crash_dump.c
60
61 /*
62 * Architectures may override this function to read from notes sections
63 */
64 ssize_t __weak elfcorehdr_read_notes(char *buf, size_t count, u64 *ppos)
65 {
66 struct kvec kvec = { .iov_base = buf, .iov_len = count };
67 struct iov_iter iter;
68
69 if (!is_kdump_kernel()) {
70 memcpy(buf, __va(*ppos), count);
71 return count;
72 }
73
74 iov_iter_kvec(&iter, ITER_DEST, &kvec, 1, count);
75
76 return read_from_oldmem(&iter, count, ppos,
> 77 cc_platform_has(CC_ATTR_MEM_ENCRYPT));
78 }
79
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-10 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 15:00 [RFC PATCH 0/4 v1] LPC materials: livedump Lukas Hruska
2023-11-10 15:00 ` [RFC PATCH 1/4 v1] crash/vmcore: VMCOREINFO creation from non-kdump kernel Lukas Hruska
2023-11-10 21:56 ` kernel test robot
2023-11-10 23:26 ` kernel test robot [this message]
2023-11-10 15:00 ` [RFC PATCH 2/4 v1] livedump: Add write protection management Lukas Hruska
2023-11-11 5:20 ` kernel test robot
2023-11-10 15:00 ` [RFC PATCH 3/4 v1] livedump: Add memory dumping functionality Lukas Hruska
2023-11-11 15:06 ` kernel test robot
2023-11-11 19:19 ` kernel test robot
2023-11-10 15:00 ` [RFC PATCH 4/4 v1] livedump: Add tools to make livedump creation easier Lukas Hruska
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=202311110746.PACzMVRq-lkp@intel.com \
--to=lkp@intel.com \
--cc=lhruska@suse.cz \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.