All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Fan Wu <wufan@linux.microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v11 04/19] ipe: add LSM hooks on execution and kernel read
Date: Thu, 5 Oct 2023 16:24:35 +0800	[thread overview]
Message-ID: <202310051601.vuZh1VMf-lkp@intel.com> (raw)
In-Reply-To: <1696457386-3010-5-git-send-email-wufan@linux.microsoft.com>

Hi Fan,

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

[auto build test WARNING on device-mapper-dm/for-next]
[also build test WARNING on axboe-block/for-next lwn/docs-next linus/master v6.6-rc4 next-20231005]
[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/Fan-Wu/security-add-ipe-lsm/20231005-061243
base:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
patch link:    https://lore.kernel.org/r/1696457386-3010-5-git-send-email-wufan%40linux.microsoft.com
patch subject: [RFC PATCH v11 04/19] ipe: add LSM hooks on execution and kernel read
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20231005/202310051601.vuZh1VMf-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231005/202310051601.vuZh1VMf-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/202310051601.vuZh1VMf-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> security/ipe/hooks.c:51: warning: Function parameter or member '__always_unused' not described in 'ipe_mmap_file'
>> security/ipe/hooks.c:51: warning: Excess function parameter 'reqprot' description in 'ipe_mmap_file'
>> security/ipe/hooks.c:79: warning: Function parameter or member '__always_unused' not described in 'ipe_file_mprotect'
>> security/ipe/hooks.c:79: warning: Excess function parameter 'reqprot' description in 'ipe_file_mprotect'


vim +51 security/ipe/hooks.c

    33	
    34	/**
    35	 * ipe_mmap_file - ipe security hook function for mmap check.
    36	 * @f: File being mmap'd. Can be NULL in the case of anonymous memory.
    37	 * @reqprot: The requested protection on the mmap, passed from usermode.
    38	 * @prot: The effective protection on the mmap, resolved from reqprot and
    39	 *	  system configuration.
    40	 * @flags: Unused.
    41	 *
    42	 * This hook is called when a file is loaded through the mmap
    43	 * family of system calls.
    44	 *
    45	 * Return:
    46	 * * 0	- OK
    47	 * * !0	- Error
    48	 */
    49	int ipe_mmap_file(struct file *f, unsigned long reqprot __always_unused,
    50			  unsigned long prot, unsigned long flags)
  > 51	{
    52		struct ipe_eval_ctx ctx = IPE_EVAL_CTX_INIT;
    53	
    54		if (prot & PROT_EXEC) {
    55			build_eval_ctx(&ctx, f, IPE_OP_EXEC);
    56			return ipe_evaluate_event(&ctx);
    57		}
    58	
    59		return 0;
    60	}
    61	
    62	/**
    63	 * ipe_file_mprotect - ipe security hook function for mprotect check.
    64	 * @vma: Existing virtual memory area created by mmap or similar.
    65	 * @reqprot: The requested protection on the mmap, passed from usermode.
    66	 * @prot: The effective protection on the mmap, resolved from reqprot and
    67	 *	  system configuration.
    68	 *
    69	 * This LSM hook is called when a mmap'd region of memory is changing
    70	 * its protections via mprotect.
    71	 *
    72	 * Return:
    73	 * * 0	- OK
    74	 * * !0	- Error
    75	 */
    76	int ipe_file_mprotect(struct vm_area_struct *vma,
    77			      unsigned long reqprot __always_unused,
    78			      unsigned long prot)
  > 79	{
    80		struct ipe_eval_ctx ctx = IPE_EVAL_CTX_INIT;
    81	
    82		/* Already Executable */
    83		if (vma->vm_flags & VM_EXEC)
    84			return 0;
    85	
    86		if (prot & PROT_EXEC) {
    87			build_eval_ctx(&ctx, vma->vm_file, IPE_OP_EXEC);
    88			return ipe_evaluate_event(&ctx);
    89		}
    90	
    91		return 0;
    92	}
    93	

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

  reply	other threads:[~2023-10-05  8:25 UTC|newest]

Thread overview: 105+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 22:09 [RFC PATCH v11 00/19] Integrity Policy Enforcement LSM (IPE) Fan Wu
2023-10-04 22:09 ` [dm-devel] " Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 01/19] security: add ipe lsm Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 02/19] ipe: add policy parser Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC v11 2/19] " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-10-25 22:45     ` Fan Wu
2023-10-25 22:45       ` Fan Wu
2023-10-26 21:36       ` Paul Moore
2023-10-26 21:36         ` Paul Moore
2023-10-04 22:09 ` [RFC PATCH v11 03/19] ipe: add evaluation loop Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC v11 3/19] " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-10-26  0:15     ` Fan Wu
2023-10-26  0:15       ` Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 04/19] ipe: add LSM hooks on execution and kernel read Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-05  8:24   ` kernel test robot [this message]
2023-10-24  3:52   ` [PATCH RFC v11 4/19] " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-10-04 22:09 ` [RFC PATCH v11 05/19] ipe: introduce 'boot_verified' as a trust provider Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC v11 5/19] " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-10-26 21:33     ` Fan Wu
2023-10-26 21:33       ` Fan Wu
2023-10-26 22:12       ` Paul Moore
2023-10-26 22:12         ` Paul Moore
2023-11-02 22:46         ` Fan Wu
2023-11-03 22:15           ` Paul Moore
2023-11-03 22:30             ` Paul Moore
2023-10-04 22:09 ` [RFC PATCH v11 06/19] security: add new securityfs delete function Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 07/19] ipe: add userspace interface Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-05 10:32   ` kernel test robot
2023-10-24  3:52   ` [PATCH RFC v11 7/19] " Paul Moore
2023-10-04 22:09 ` [RFC PATCH v11 08/19] uapi|audit|ipe: add ipe auditing support Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-05 13:00   ` kernel test robot
2023-10-24  3:52   ` [PATCH RFC v11 8/19] " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02 22:55     ` Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 09/19] ipe: add permissive toggle Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC v11 9/19] " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02 22:56     ` Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 10/19] block|security: add LSM blob to block_device Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 11/19] dm verity: set DM_TARGET_SINGLETON feature flag Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02  0:40     ` Paul Moore
2023-10-04 22:09 ` [RFC PATCH v11 12/19] dm: add finalize hook to target_type Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02  0:41     ` Paul Moore
2023-10-04 22:09 ` [RFC PATCH v11 13/19] dm verity: consume root hash digest and signature data via LSM hook Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02  0:41     ` Paul Moore
2023-10-04 22:09 ` [RFC PATCH v11 14/19] ipe: add support for dm-verity as a trust provider Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02 22:40     ` Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 15/19] fsverity: consume builtin signature via LSM hook Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-05  2:27   ` Eric Biggers
2023-10-05  2:27     ` [dm-devel] " Eric Biggers
2023-10-05  2:49     ` Fan Wu
2023-10-05  2:49       ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02  0:40     ` Paul Moore
2023-11-02  2:53       ` Eric Biggers
2023-11-02 15:42         ` Paul Moore
2023-11-02 19:33           ` Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 16/19] ipe: enable support for fs-verity as a trust provider Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-04 23:58   ` Randy Dunlap
2023-10-04 23:58     ` [dm-devel] " Randy Dunlap
2023-10-05  2:45     ` Fan Wu
2023-10-05  2:45       ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-10-04 22:09 ` [RFC PATCH v11 17/19] scripts: add boot policy generation program Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02 23:09     ` Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 18/19] ipe: kunit test for parser Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu
2023-10-24  3:52   ` [PATCH RFC " Paul Moore
2023-10-24  3:52     ` Paul Moore
2023-11-02 23:11     ` Fan Wu
2023-10-04 22:09 ` [RFC PATCH v11 19/19] documentation: add ipe documentation Fan Wu
2023-10-04 22:09   ` [dm-devel] " Fan Wu

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=202310051601.vuZh1VMf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=wufan@linux.microsoft.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.