linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>, linux-integrity@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, "Mimi Zohar" <zohar@linux.ibm.com>,
	=?unknown-8bit?Q?Micka=C3=ABl_Sala=C3=BCn?= <mic@digikod.net>,
	roberto.sassu@huawei.com, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ima: instantiate the bprm_creds_for_exec() hook
Date: Thu, 28 Nov 2024 23:57:04 +0800	[thread overview]
Message-ID: <202411282320.KuWvLpDS-lkp@intel.com> (raw)
In-Reply-To: <20241127210234.121546-1-zohar@linux.ibm.com>

Hi Mimi,

kernel test robot noticed the following build errors:

[auto build test ERROR on zohar-integrity/next-integrity]
[also build test ERROR on linus/master v6.12 next-20241128]
[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/Mimi-Zohar/ima-instantiate-the-bprm_creds_for_exec-hook/20241128-120656
base:   https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
patch link:    https://lore.kernel.org/r/20241127210234.121546-1-zohar%40linux.ibm.com
patch subject: [PATCH] ima: instantiate the bprm_creds_for_exec() hook
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20241128/202411282320.KuWvLpDS-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/20241128/202411282320.KuWvLpDS-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/202411282320.KuWvLpDS-lkp@intel.com/

All errors (new ones prefixed by >>):

   security/integrity/ima/ima_main.c: In function 'ima_bprm_creds_for_exec':
>> security/integrity/ima/ima_main.c:572:18: error: 'struct linux_binprm' has no member named 'is_check'
     572 |         if (!bprm->is_check)
         |                  ^~
--
   security/integrity/ima/ima_appraise.c: In function 'is_bprm_creds_for_exec':
>> security/integrity/ima/ima_appraise.c:492:25: error: 'struct linux_binprm' has no member named 'is_check'
     492 |                 if (bprm->is_check)
         |                         ^~


vim +572 security/integrity/ima/ima_main.c

   556	
   557	/**
   558	 * ima_bprm_creds_for_exec - based on policy, collect/store/appraise measurement.
   559	 * @bprm: contains the linux_binprm structure
   560	 *
   561	 * Based on the IMA policy and the execvat(2) AT_CHECK flag, measure and
   562	 * appraise the integrity of a file to be executed by script interpreters.
   563	 * Unlike any of the other LSM hooks where the kernel enforces file integrity,
   564	 * enforcing file integrity is left up to the discretion of the script
   565	 * interpreter (userspace).
   566	 *
   567	 * On success return 0.  On integrity appraisal error, assuming the file
   568	 * is in policy and IMA-appraisal is in enforcing mode, return -EACCES.
   569	 */
   570	static int ima_bprm_creds_for_exec(struct linux_binprm *bprm)
   571	{
 > 572		if (!bprm->is_check)
   573			return 0;
   574	
   575		return ima_bprm_check(bprm);
   576	}
   577	

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

  reply	other threads:[~2024-11-28 15:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 21:02 [PATCH] ima: instantiate the bprm_creds_for_exec() hook Mimi Zohar
2024-11-28 15:57 ` kernel test robot [this message]
2024-11-28 21:07 ` kernel test robot
2024-11-29 11:06 ` Mickaël Salaün
2024-12-02 19:40   ` Mimi Zohar
2024-12-03 11:53     ` Mickaël Salaün
2024-12-03 16:03       ` Mimi Zohar
2024-12-02 21:25 ` Stefan Berger
2024-12-03 11:58 ` Mickaël Salaün

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=202411282320.KuWvLpDS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=roberto.sassu@huawei.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).