From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com,
Guenter Roeck <groeck@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 5/9] security/chromiumos/lsm.c:363:16: error: no member named 'path_mknod' in 'struct security_hook_heads'
Date: Wed, 13 Dec 2023 06:17:11 +0800 [thread overview]
Message-ID: <202312130647.qRhLaIvL-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: 551feb341e3983286656590b35b7d25d4c6f330c
commit: a3f9cabfd60ea603dab3d0d8bc864d97227a9069 [5/9] CHROMIUM: security: Add a DM LSM
config: x86_64-randconfig-075-20231213 (https://download.01.org/0day-ci/archive/20231213/202312130647.qRhLaIvL-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231213/202312130647.qRhLaIvL-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/202312130647.qRhLaIvL-lkp@intel.com/
All errors (new ones prefixed by >>):
>> security/chromiumos/lsm.c:363:16: error: no member named 'path_mknod' in 'struct security_hook_heads'
LSM_HOOK_INIT(path_mknod, chromiumos_security_path_mknod),
~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/lsm_hooks.h:101:33: note: expanded from macro 'LSM_HOOK_INIT'
{ .head = &security_hook_heads.HEAD, .hook = { .HEAD = HOOK } }
~~~~~~~~~~~~~~~~~~~ ^
1 error generated.
vim +363 security/chromiumos/lsm.c
354
355
356 static struct security_hook_list chromiumos_security_hooks[] = {
357 LSM_HOOK_INIT(sb_mount, chromiumos_security_sb_mount),
358 LSM_HOOK_INIT(inode_follow_link, chromiumos_security_inode_follow_link),
359 LSM_HOOK_INIT(file_open, chromiumos_security_file_open),
360 LSM_HOOK_INIT(sb_eat_lsm_opts, chromiumos_sb_eat_lsm_opts),
361 LSM_HOOK_INIT(bprm_creds_for_exec, chromiumos_bprm_creds_for_exec),
362 LSM_HOOK_INIT(locked_down, chromiumos_locked_down),
> 363 LSM_HOOK_INIT(path_mknod, chromiumos_security_path_mknod),
364 LSM_HOOK_INIT(inode_mknod, chromiumos_security_inode_mknod),
365 };
366
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-12 22:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202312130647.qRhLaIvL-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=groeck@google.com \
--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 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.