From: kernel test robot <lkp@intel.com>
To: "Maxime Bélair" <maxime.belair@canonical.com>,
linux-security-module@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
john.johansen@canonical.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com, mic@digikod.net,
kees@kernel.org, stephen.smalley.work@gmail.com,
casey@schaufler-ca.com, takedakn@nttdata.co.jp,
penguin-kernel@i-love.sakura.ne.jp, linux-api@vger.kernel.org,
apparmor@lists.ubuntu.com, linux-kernel@vger.kernel.org,
"Maxime Bélair" <maxime.belair@canonical.com>
Subject: Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
Date: Wed, 7 May 2025 21:58:03 +0800 [thread overview]
Message-ID: <202505072131.ogtsaLPI-lkp@intel.com> (raw)
In-Reply-To: <20250506143254.718647-2-maxime.belair@canonical.com>
Hi Maxime,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 9c32cda43eb78f78c73aee4aa344b777714e259b]
url: https://github.com/intel-lab-lkp/linux/commits/Maxime-B-lair/Wire-up-the-lsm_manage_policy-syscall/20250506-224212
base: 9c32cda43eb78f78c73aee4aa344b777714e259b
patch link: https://lore.kernel.org/r/20250506143254.718647-2-maxime.belair%40canonical.com
patch subject: [PATCH 1/3] Wire up the lsm_manage_policy syscall
config: s390-allnoconfig (https://download.01.org/0day-ci/archive/20250507/202505072131.ogtsaLPI-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250507/202505072131.ogtsaLPI-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/202505072131.ogtsaLPI-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> <stdin>:1618:2: warning: syscall lsm_manage_policy not implemented [-W#warnings]
1618 | #warning syscall lsm_manage_policy not implemented
| ^
1 warning generated.
--
>> <stdin>:1618:2: warning: syscall lsm_manage_policy not implemented [-W#warnings]
1618 | #warning syscall lsm_manage_policy not implemented
| ^
1 warning generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-07 13:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 14:32 [PATCH 0/3] lsm: introduce lsm_manage_policy() syscall Maxime Bélair
2025-05-06 14:32 ` [PATCH 1/3] Wire up the lsm_manage_policy syscall Maxime Bélair
2025-05-07 6:26 ` Song Liu
2025-05-07 15:37 ` Maxime Bélair
2025-05-07 22:04 ` Tetsuo Handa
2025-05-08 7:52 ` John Johansen
2025-05-09 10:25 ` Mickaël Salaün
2025-05-11 11:09 ` John Johansen
2025-05-08 6:06 ` Song Liu
2025-05-08 8:18 ` John Johansen
2025-05-09 10:26 ` Mickaël Salaün
2025-05-11 10:47 ` John Johansen
2025-05-12 10:20 ` Mickaël Salaün
2025-05-17 7:59 ` John Johansen
2025-05-08 7:12 ` John Johansen
2025-05-07 13:58 ` kernel test robot [this message]
2025-05-06 14:32 ` [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook Maxime Bélair
2025-05-07 6:19 ` Song Liu
2025-05-07 15:37 ` Maxime Bélair
2025-05-08 8:20 ` John Johansen
2025-05-07 10:40 ` Tetsuo Handa
2025-05-07 15:37 ` Maxime Bélair
2025-05-07 20:25 ` Paul Moore
2025-05-08 8:29 ` John Johansen
2025-05-08 16:54 ` Casey Schaufler
2025-05-09 10:26 ` Mickaël Salaün
2025-05-09 14:21 ` Casey Schaufler
2025-05-11 11:26 ` John Johansen
2025-05-11 11:20 ` John Johansen
2025-05-08 8:25 ` John Johansen
2025-05-08 12:55 ` Tetsuo Handa
2025-05-08 14:44 ` John Johansen
2025-05-08 15:07 ` Tetsuo Handa
2025-05-09 3:25 ` John Johansen
2025-05-07 12:04 ` kernel test robot
2025-05-06 14:32 ` [PATCH 3/3] AppArmor: add support for lsm_manage_policy Maxime Bélair
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=202505072131.ogtsaLPI-lkp@intel.com \
--to=lkp@intel.com \
--cc=apparmor@lists.ubuntu.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=kees@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maxime.belair@canonical.com \
--cc=mic@digikod.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.com \
--cc=takedakn@nttdata.co.jp \
/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).