From: kernel test robot <lkp@intel•com>
To: Vignesh Balasubramanian <vigbalas@amd•com>,
linux-kernel@vger•kernel.org, linux-toolchains@vger•kernel.org
Cc: felix.willgerodt@intel•com, x86@kernel•org,
keescook@chromium•org, jhb@freebsd•org, bpetkov@amd•com,
binutils@sourceware•org, llvm@lists•linux.dev,
christophe.leroy@csgroup•eu, aneesh.kumar@kernel•org,
linux-mm@kvack•org, Vignesh Balasubramanian <vigbalas@amd•com>,
npiggin@gmail•com, oe-kbuild-all@lists•linux.dev,
naveen.n.rao@linux•ibm.com, Borislav Petkov <bp@alien8•de>,
tglx@linutronix•de, linuxppc-dev@lists•ozlabs.org,
jinisusan.george@amd•com, matz@suse•de, ebiederm@xmission•com
Subject: Re: [PATCH v4 1/1] x86/elf: Add a new .note section containing xfeatures buffer layout info to x86 core files
Date: Wed, 24 Jul 2024 06:46:19 +0800 [thread overview]
Message-ID: <202407240659.eRyEDmG1-lkp@intel.com> (raw)
In-Reply-To: <20240723090454.8241-2-vigbalas@amd.com>
Hi Vignesh,
kernel test robot noticed the following build errors:
[auto build test ERROR on kees/for-next/execve]
[also build test ERROR on tip/x86/core kees/for-next/pstore kees/for-next/kspp linus/master v6.10 next-20240723]
[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/Vignesh-Balasubramanian/x86-elf-Add-a-new-note-section-containing-xfeatures-buffer-layout-info-to-x86-core-files/20240723-170946
base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/execve
patch link: https://lore.kernel.org/r/20240723090454.8241-2-vigbalas%40amd.com
patch subject: [PATCH v4 1/1] x86/elf: Add a new .note section containing xfeatures buffer layout info to x86 core files
config: x86_64-buildonly-randconfig-005-20240724 (https://download.01.org/0day-ci/archive/20240724/202407240659.eRyEDmG1-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240724/202407240659.eRyEDmG1-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/202407240659.eRyEDmG1-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <built-in>:1:
./usr/include/asm/elf.h:6:2: error: unknown type name 'u32'
6 | u32 type;
| ^
./usr/include/asm/elf.h:7:2: error: unknown type name 'u32'
7 | u32 size;
| ^
./usr/include/asm/elf.h:8:2: error: unknown type name 'u32'
8 | u32 offset;
| ^
./usr/include/asm/elf.h:9:2: error: unknown type name 'u32'
9 | u32 flags;
| ^
>> ./usr/include/asm/elf.h:12:16: error: static assertion failed due to requirement 'sizeof(struct x86_xfeat_component) % 4 == 0': x86_xfeat_component is not aligned
12 | _Static_assert(sizeof(struct x86_xfeat_component)%4 == 0, "x86_xfeat_component is not aligned");
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./usr/include/asm/elf.h:12:53: note: expression evaluates to '1 == 0'
12 | _Static_assert(sizeof(struct x86_xfeat_component)%4 == 0, "x86_xfeat_component is not aligned");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
5 errors generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-07-23 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 9:04 [PATCH v4 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts Vignesh Balasubramanian
2024-07-23 9:04 ` [PATCH v4 1/1] x86/elf: Add a new .note section containing xfeatures buffer layout info to x86 core files Vignesh Balasubramanian
2024-07-23 22:46 ` kernel test robot [this message]
2024-07-23 22: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=202407240659.eRyEDmG1-lkp@intel.com \
--to=lkp@intel$(echo .)com \
--cc=aneesh.kumar@kernel$(echo .)org \
--cc=binutils@sourceware$(echo .)org \
--cc=bp@alien8$(echo .)de \
--cc=bpetkov@amd$(echo .)com \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=ebiederm@xmission$(echo .)com \
--cc=felix.willgerodt@intel$(echo .)com \
--cc=jhb@freebsd$(echo .)org \
--cc=jinisusan.george@amd$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-toolchains@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=matz@suse$(echo .)de \
--cc=naveen.n.rao@linux$(echo .)ibm.com \
--cc=npiggin@gmail$(echo .)com \
--cc=oe-kbuild-all@lists$(echo .)linux.dev \
--cc=tglx@linutronix$(echo .)de \
--cc=vigbalas@amd$(echo .)com \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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