From: kernel test robot <lkp@intel.com>
To: John Johansen <john.johansen@canonical.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jj-apparmor:apparmor-next 4/4] security/apparmor/af_unix.c:604:3: error: call to undeclared function 'unix_state_lock_nested'; ISO C99 and later do not support implicit function declarations
Date: Tue, 30 Jul 2024 08:05:36 +0800 [thread overview]
Message-ID: <202407300828.EbdfjLX0-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor.git apparmor-next
head: e6b2ff78a1aeb16f290e483536dedf626ba2d1e9
commit: e6b2ff78a1aeb16f290e483536dedf626ba2d1e9 [4/4] apparmor: add fine grained af_unix mediation
config: i386-buildonly-randconfig-004-20240730 (https://download.01.org/0day-ci/archive/20240730/202407300828.EbdfjLX0-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240730/202407300828.EbdfjLX0-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/202407300828.EbdfjLX0-lkp@intel.com/
All errors (new ones prefixed by >>):
>> security/apparmor/af_unix.c:604:3: error: call to undeclared function 'unix_state_lock_nested'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
604 | unix_state_lock_nested(sk2, U_LOCK_SECOND);
| ^
>> security/apparmor/af_unix.c:604:31: error: use of undeclared identifier 'U_LOCK_SECOND'
604 | unix_state_lock_nested(sk2, U_LOCK_SECOND);
| ^
security/apparmor/af_unix.c:607:3: error: call to undeclared function 'unix_state_lock_nested'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
607 | unix_state_lock_nested(sk1, U_LOCK_SECOND);
| ^
security/apparmor/af_unix.c:607:31: error: use of undeclared identifier 'U_LOCK_SECOND'
607 | unix_state_lock_nested(sk1, U_LOCK_SECOND);
| ^
4 errors generated.
vim +/unix_state_lock_nested +604 security/apparmor/af_unix.c
595
596 static void unix_state_double_lock(struct sock *sk1, struct sock *sk2)
597 {
598 if (unlikely(sk1 == sk2) || !sk2) {
599 unix_state_lock(sk1);
600 return;
601 }
602 if (sk1 < sk2) {
603 unix_state_lock(sk1);
> 604 unix_state_lock_nested(sk2, U_LOCK_SECOND);
605 } else {
606 unix_state_lock(sk2);
607 unix_state_lock_nested(sk1, U_LOCK_SECOND);
608 }
609 }
610
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-30 0:06 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=202407300828.EbdfjLX0-lkp@intel.com \
--to=lkp@intel.com \
--cc=john.johansen@canonical.com \
--cc=llvm@lists.linux.dev \
--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