linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: steven chen <chenste@linux.microsoft.com>,
	zohar@linux.ibm.com, stefanb@linux.ibm.com,
	roberto.sassu@huaweicloud.com, roberto.sassu@huawei.com,
	eric.snowberg@oracle.com, ebiederm@xmission.com,
	paul@paul-moore.com, code@tyhicks.com, bauermann@kolabnow.com,
	linux-integrity@vger.kernel.org, kexec@lists.infradead.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, madvenka@linux.microsoft.com,
	nramas@linux.microsoft.com,
	James.Bottomley@hansenpartnership.com, bhe@redhat.com,
	vgoyal@redhat.com, dyoung@redhat.com
Subject: Re: [PATCH v8 2/7] kexec: define functions to map and unmap segments
Date: Thu, 20 Feb 2025 08:53:48 +0800	[thread overview]
Message-ID: <202502200848.MJEuphR1-lkp@intel.com> (raw)
In-Reply-To: <20250218225502.747963-3-chenste@linux.microsoft.com>

Hi steven,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.14-rc3 next-20250219]
[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/steven-chen/ima-define-and-call-ima_alloc_kexec_file_buf/20250219-065931
base:   linus/master
patch link:    https://lore.kernel.org/r/20250218225502.747963-3-chenste%40linux.microsoft.com
patch subject: [PATCH v8 2/7] kexec: define functions to map and unmap segments
config: x86_64-buildonly-randconfig-004-20250220 (https://download.01.org/0day-ci/archive/20250220/202502200848.MJEuphR1-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250220/202502200848.MJEuphR1-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/202502200848.MJEuphR1-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from include/linux/crash_dump.h:5,
                    from mm/mm_init.c:30:
>> include/linux/kexec.h:479:47: warning: 'struct kimage' declared inside parameter list will not be visible outside of this definition or declaration
     479 | static inline void *kimage_map_segment(struct kimage *image, unsigned long addr, unsigned long size)
         |                                               ^~~~~~


vim +479 include/linux/kexec.h

   466	
   467	#define kexec_dprintk(fmt, arg...) \
   468	        do { if (kexec_file_dbg_print) pr_info(fmt, ##arg); } while (0)
   469	
   470	extern void *kimage_map_segment(struct kimage *image, unsigned long addr, unsigned long size);
   471	extern void kimage_unmap_segment(void *buffer);
   472	#else /* !CONFIG_KEXEC_CORE */
   473	struct pt_regs;
   474	struct task_struct;
   475	static inline void __crash_kexec(struct pt_regs *regs) { }
   476	static inline void crash_kexec(struct pt_regs *regs) { }
   477	static inline int kexec_should_crash(struct task_struct *p) { return 0; }
   478	static inline int kexec_crash_loaded(void) { return 0; }
 > 479	static inline void *kimage_map_segment(struct kimage *image, unsigned long addr, unsigned long size)
   480	{ return NULL; }
   481	static inline void kimage_unmap_segment(void *buffer) { }
   482	#define kexec_in_progress false
   483	#endif /* CONFIG_KEXEC_CORE */
   484	

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

  reply	other threads:[~2025-02-20  0:54 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 22:54 [PATCH v8 0/7] ima: kexec: measure events between kexec load and execute steven chen
2025-02-18 22:54 ` [PATCH v8 1/7] ima: define and call ima_alloc_kexec_file_buf steven chen
2025-02-20 14:53   ` Mimi Zohar
2025-02-20 15:04     ` James Bottomley
2025-02-20 16:23       ` Mimi Zohar
2025-02-21 21:02         ` steven chen
2025-02-18 22:54 ` [PATCH v8 2/7] kexec: define functions to map and unmap segments steven chen
2025-02-20  0:53   ` kernel test robot [this message]
2025-02-20 17:22   ` Mimi Zohar
2025-02-21 21:05     ` steven chen
2025-02-24  6:14   ` Baoquan He
2025-02-24 23:05     ` steven chen
2025-02-25  0:18       ` Baoquan He
2025-02-25 18:35         ` steven chen
2025-02-26  0:39           ` Baoquan He
2025-02-27 15:41     ` Mimi Zohar
2025-02-28  5:03       ` Baoquan He
2025-03-04 16:15         ` Mimi Zohar
2025-02-18 22:54 ` [PATCH v8 3/7] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
2025-02-21 15:41   ` Mimi Zohar
2025-02-21 21:06     ` steven chen
2025-02-18 22:54 ` [PATCH v8 4/7] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-02-19 15:37   ` Stefan Berger
2025-02-19 19:21     ` steven chen
2025-02-21 19:07   ` Mimi Zohar
2025-02-21 19:41     ` Stefan Berger
2025-02-18 22:55 ` [PATCH v8 5/7] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-02-19 15:57   ` Stefan Berger
2025-02-19 19:23     ` steven chen
2025-02-20  1:35   ` kernel test robot
2025-02-18 22:55 ` [PATCH v8 6/7] ima: make the kexec extra memory configurable steven chen
2025-02-20 21:36   ` Mimi Zohar
2025-02-18 22:55 ` [PATCH v8 7/7] ima: measure kexec load and exec events as critical data steven chen
2025-02-19 16:23   ` Stefan Berger
2025-02-19 19:24     ` steven chen
2025-02-21  0:46   ` Mimi Zohar
2025-02-21 21:10     ` 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=202502200848.MJEuphR1-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=bauermann@kolabnow.com \
    --cc=bhe@redhat.com \
    --cc=chenste@linux.microsoft.com \
    --cc=code@tyhicks.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=eric.snowberg@oracle.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=madvenka@linux.microsoft.com \
    --cc=nramas@linux.microsoft.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paul@paul-moore.com \
    --cc=roberto.sassu@huawei.com \
    --cc=roberto.sassu@huaweicloud.com \
    --cc=stefanb@linux.ibm.com \
    --cc=vgoyal@redhat.com \
    --cc=zohar@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).