From: kernel test robot <lkp@intel.com>
To: Usama Arif <usamaarif642@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Date: Fri, 10 Jan 2025 14:56:38 +0800 [thread overview]
Message-ID: <202501101406.jEd6Y91q-lkp@intel.com> (raw)
In-Reply-To: <20250108215957.3437660-3-usamaarif642@gmail.com>
Hi Usama,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on efi/next]
[also build test ERROR on linus/master v6.13-rc6 next-20250109]
[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/Usama-Arif/efi-memattr-Use-desc_size-instead-of-total-size-to-check-for-corruption/20250109-060158
base: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
patch link: https://lore.kernel.org/r/20250108215957.3437660-3-usamaarif642%40gmail.com
patch subject: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
config: i386-buildonly-randconfig-002-20250110 (https://download.01.org/0day-ci/archive/20250110/202501101406.jEd6Y91q-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250110/202501101406.jEd6Y91q-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/202501101406.jEd6Y91q-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/x86/platform/efi/efi.c:39:
In file included from include/linux/memblock.h:12:
In file included from include/linux/mm.h:2223:
include/linux/vmstat.h:504:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
504 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
505 | item];
| ~~~~
include/linux/vmstat.h:511:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
511 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
512 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
include/linux/vmstat.h:524:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
524 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
525 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
>> arch/x86/platform/efi/efi.c:169:6: error: redefinition of 'arch_update_firmware_area'
169 | void arch_update_firmware_area(u64 addr, u64 size)
| ^
include/linux/efi.h:1360:27: note: previous definition is here
1360 | static inline void __init arch_update_firmware_area(u64 addr, u64 size)
| ^
4 warnings and 1 error generated.
vim +/arch_update_firmware_area +169 arch/x86/platform/efi/efi.c
167
168 /* Reserve firmware area if it was marked as RAM */
> 169 void arch_update_firmware_area(u64 addr, u64 size)
170 {
171 if (e820__get_entry_type(addr, addr + size) == E820_TYPE_RAM) {
172 e820__range_update_firmware(addr, size, E820_TYPE_RAM, E820_TYPE_RESERVED);
173 e820__update_table(e820_table_firmware);
174 }
175 }
176
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-01-10 6:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 21:53 [RFC 0/2] efi/memattr: Fix memory corruption and warning issues Usama Arif
2025-01-08 21:53 ` [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption Usama Arif
2025-01-09 15:45 ` Ard Biesheuvel
2025-01-09 16:36 ` Usama Arif
2025-01-10 7:21 ` Ard Biesheuvel
2025-01-10 10:53 ` Usama Arif
2025-01-10 17:25 ` Ard Biesheuvel
2025-01-13 2:33 ` Dave Young
2025-01-13 11:27 ` Usama Arif
2025-01-13 12:00 ` Usama Arif
2025-01-20 10:27 ` Usama Arif
2025-01-20 10:32 ` Ard Biesheuvel
2025-01-20 10:50 ` Usama Arif
2025-01-20 11:29 ` Ard Biesheuvel
2025-01-20 11:48 ` Usama Arif
2025-01-22 5:36 ` Dave Young
2025-01-22 11:50 ` Usama Arif
2025-01-08 21:53 ` [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware Usama Arif
2025-01-09 16:15 ` Ard Biesheuvel
2025-01-09 16:32 ` Usama Arif
2025-01-09 16:47 ` Gregory Price
2025-01-10 7:32 ` Ard Biesheuvel
2025-01-10 11:36 ` Breno Leitao
2025-01-10 17:33 ` Ard Biesheuvel
2025-01-10 14:31 ` Usama Arif
2025-01-10 15:50 ` Usama Arif
2025-01-10 2:50 ` Dave Young
2025-01-10 11:12 ` Usama Arif
2025-01-10 11:18 ` Dave Young
2025-01-10 11:20 ` Dave Young
2025-01-10 11:42 ` Usama Arif
2025-01-10 6:56 ` kernel test robot [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=202501101406.jEd6Y91q-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=usamaarif642@gmail.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 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.