From: kernel test robot <lkp@intel.com>
To: Konstantin Meskhidze <konstantin.meskhidze@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Mickaël Salaün" <mic@digikod.net>
Subject: [linux-next:master 12600/13086] security/landlock/net.h:26:1: warning: 'landlock_append_net_rule' declared 'static' but never defined
Date: Tue, 17 Oct 2023 17:05:06 +0800 [thread overview]
Message-ID: <202310171657.KGpaQG47-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4d5ab2376ec576af173e5eac3887ed0b51bd8566
commit: 614d46b333ab905ca99acf076e4abdc84afd3da7 [12600/13086] landlock: Add network rules and TCP hooks support
config: microblaze-randconfig-r004-20230514 (https://download.01.org/0day-ci/archive/20231017/202310171657.KGpaQG47-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231017/202310171657.KGpaQG47-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/202310171657.KGpaQG47-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from security/landlock/setup.c:17:
security/landlock/net.h:28:1: error: expected identifier or '(' before '{' token
28 | {
| ^
>> security/landlock/net.h:26:1: warning: 'landlock_append_net_rule' declared 'static' but never defined [-Wunused-function]
26 | landlock_append_net_rule(struct landlock_ruleset *const ruleset, const u16 port,
| ^~~~~~~~~~~~~~~~~~~~~~~~
--
In file included from security/landlock/syscalls.c:32:
security/landlock/net.h:28:1: error: expected identifier or '(' before '{' token
28 | {
| ^
>> security/landlock/net.h:26:1: warning: 'landlock_append_net_rule' used but never defined
26 | landlock_append_net_rule(struct landlock_ruleset *const ruleset, const u16 port,
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +26 security/landlock/net.h
24
25 static inline int
> 26 landlock_append_net_rule(struct landlock_ruleset *const ruleset, const u16 port,
27 access_mask_t access_rights);
> 28 {
29 return -EAFNOSUPPORT;
30 }
31 #endif /* IS_ENABLED(CONFIG_INET) */
32
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-17 9:05 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=202310171657.KGpaQG47-lkp@intel.com \
--to=lkp@intel.com \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-mm@kvack.org \
--cc=mic@digikod.net \
--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