From: kernel test robot <lkp@intel.com>
To: Tingmao Wang <m@maowtm.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 6/9] Creating supervisor events for filesystem operations
Date: Wed, 5 Mar 2025 13:05:37 +0800 [thread overview]
Message-ID: <202503051227.Dhb3OX2X-lkp@intel.com> (raw)
In-Reply-To: <ed5904af2bdab297f4137a43e44363721894f42f.1741047969.git.m@maowtm.org>
Hi Tingmao,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.14-rc5 next-20250304]
[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/Tingmao-Wang/Define-the-supervisor-and-event-structure/20250304-092354
base: linus/master
patch link: https://lore.kernel.org/r/ed5904af2bdab297f4137a43e44363721894f42f.1741047969.git.m%40maowtm.org
patch subject: [RFC PATCH 6/9] Creating supervisor events for filesystem operations
config: i386-buildonly-randconfig-003-20250305 (https://download.01.org/0day-ci/archive/20250305/202503051227.Dhb3OX2X-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250305/202503051227.Dhb3OX2X-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/202503051227.Dhb3OX2X-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'domain' not described in 'landlock_ask_supervised_layers'
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'denied_layers' not described in 'landlock_ask_supervised_layers'
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'request_type' not described in 'landlock_ask_supervised_layers'
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'access_request' not described in 'landlock_ask_supervised_layers'
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'path1' not described in 'landlock_ask_supervised_layers'
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'path2' not described in 'landlock_ask_supervised_layers'
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'path1_new' not described in 'landlock_ask_supervised_layers'
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'path2_new' not described in 'landlock_ask_supervised_layers'
>> security/landlock/supervise.c:97: warning: Function parameter or struct member 'port' not described in 'landlock_ask_supervised_layers'
vim +97 security/landlock/supervise.c
79
80 /**
81 * landlock_ask_supervised_layers - check if all denied layers
82 * are supervised, and if yes, ask all of them for permission.
83 *
84 * Return whether access should be allowed. If denied_layers
85 * contains any non-supervised layer, will return false without
86 * making any supervisor event.
87 *
88 * Caller owns any paths passed in, we might get refs.
89 */
90 bool landlock_ask_supervised_layers(
91 const struct landlock_ruleset *const domain,
92 const layer_mask_t denied_layers,
93 const landlock_supervise_event_type_t request_type,
94 const access_mask_t access_request, const struct path *const path1,
95 const struct path *const path2, const bool path1_new,
96 const bool path2_new, const __u16 port)
> 97 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-03-05 5:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ed5904af2bdab297f4137a43e44363721894f42f.1741047969.git.m@maowtm.org>]
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=202503051227.Dhb3OX2X-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=m@maowtm.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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