All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC][PATCH v2] ima: Add support for staging measurements for deletion and trimming
Date: Tue, 16 Dec 2025 01:00:55 +0100	[thread overview]
Message-ID: <202512160117.Red5AbKw-lkp@intel.com> (raw)
In-Reply-To: <20251212171932.316676-1-roberto.sassu@huaweicloud.com>

Hi Roberto,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on zohar-integrity/next-integrity]
[also build test ERROR on next-20251215]
[cannot apply to linus/master v6.16-rc1]
[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/Roberto-Sassu/ima-Add-support-for-staging-measurements-for-deletion-and-trimming/20251213-012318
base:   https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
patch link:    https://lore.kernel.org/r/20251212171932.316676-1-roberto.sassu%40huaweicloud.com
patch subject: [RFC][PATCH v2] ima: Add support for staging measurements for deletion and trimming
config: x86_64-rhel-9.4-ltp (https://download.01.org/0day-ci/archive/20251216/202512160117.Red5AbKw-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251216/202512160117.Red5AbKw-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/202512160117.Red5AbKw-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/linux/limits.h:7,
                    from include/linux/overflow.h:6,
                    from include/linux/bits.h:32,
                    from include/linux/ratelimit_types.h:5,
                    from include/linux/printk.h:9,
                    from include/asm-generic/bug.h:22,
                    from arch/x86/include/asm/bug.h:108,
                    from arch/x86/include/asm/alternative.h:9,
                    from arch/x86/include/asm/barrier.h:5,
                    from include/linux/list.h:11,
                    from include/linux/rculist.h:10,
                    from security/integrity/ima/ima_queue.c:18:
>> include/vdso/limits.h:13:25: error: invalid initializer
      13 | #define ULONG_MAX       (~0UL)
         |                         ^
   security/integrity/ima/ima_queue.c:43:57: note: in expansion of macro 'ULONG_MAX'
      43 | static unsigned long binary_runtime_size[BINARY_SIZE] = ULONG_MAX;
         |                                                         ^~~~~~~~~
>> security/integrity/ima/ima_queue.c:44:22: error: conflicting types for 'binary_runtime_size'; have 'long unsigned int[2]'
      44 | static unsigned long binary_runtime_size[BINARY_SIZE_FULL] = ULONG_MAX;
         |                      ^~~~~~~~~~~~~~~~~~~
   security/integrity/ima/ima_queue.c:43:22: note: previous definition of 'binary_runtime_size' with type 'long unsigned int[0]'
      43 | static unsigned long binary_runtime_size[BINARY_SIZE] = ULONG_MAX;
         |                      ^~~~~~~~~~~~~~~~~~~
>> include/vdso/limits.h:13:25: error: invalid initializer
      13 | #define ULONG_MAX       (~0UL)
         |                         ^
   security/integrity/ima/ima_queue.c:44:62: note: in expansion of macro 'ULONG_MAX'
      44 | static unsigned long binary_runtime_size[BINARY_SIZE_FULL] = ULONG_MAX;
         |                                                              ^~~~~~~~~
   security/integrity/ima/ima_queue.c:45:22: error: conflicting types for 'binary_runtime_size'; have 'long unsigned int[1]'
      45 | static unsigned long binary_runtime_size[BINARY_SIZE_STAGED] = ULONG_MAX;
         |                      ^~~~~~~~~~~~~~~~~~~
   security/integrity/ima/ima_queue.c:44:22: note: previous definition of 'binary_runtime_size' with type 'long unsigned int[2]'
      44 | static unsigned long binary_runtime_size[BINARY_SIZE_FULL] = ULONG_MAX;
         |                      ^~~~~~~~~~~~~~~~~~~
>> include/vdso/limits.h:13:25: error: invalid initializer
      13 | #define ULONG_MAX       (~0UL)
         |                         ^
   security/integrity/ima/ima_queue.c:45:64: note: in expansion of macro 'ULONG_MAX'
      45 | static unsigned long binary_runtime_size[BINARY_SIZE_STAGED] = ULONG_MAX;
         |                                                                ^~~~~~~~~


vim +44 security/integrity/ima/ima_queue.c

    35	
    36	LIST_HEAD(ima_measurements);	/* list of all measurements */
    37	LIST_HEAD(ima_measurements_staged); /* list of staged measurements */
    38	static LIST_HEAD(ima_measurements_trim); /* list of measurements to trim */
    39	bool ima_measurements_staged_exist; /* If there are staged measurements */
    40	#ifdef CONFIG_IMA_KEXEC
    41	static unsigned long binary_runtime_size[BINARY__LAST];
    42	#else
    43	static unsigned long binary_runtime_size[BINARY_SIZE] = ULONG_MAX;
  > 44	static unsigned long binary_runtime_size[BINARY_SIZE_FULL] = ULONG_MAX;
    45	static unsigned long binary_runtime_size[BINARY_SIZE_STAGED] = ULONG_MAX;
    46	#endif
    47	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-12-16  0:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12 17:19 [RFC][PATCH v2] ima: Add support for staging measurements for deletion and trimming Roberto Sassu
2025-12-12 19:41 ` steven chen
2025-12-12 22:58   ` steven chen
2025-12-13  2:06 ` Paul Moore
2025-12-15 12:41   ` Roberto Sassu
2025-12-16  0:00 ` kernel test robot [this message]
2025-12-17 15:26 ` Mimi Zohar
2025-12-17 16:01   ` Roberto Sassu
2025-12-17 19:41     ` Mimi Zohar
2026-01-28 21:30 ` steven chen
2026-01-29  8:20   ` Roberto Sassu
2026-02-11  0:09     ` steven chen

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=202512160117.Red5AbKw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=roberto.sassu@huaweicloud.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.