From: kernel test robot <lkp@intel.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [amir73il:vfs-fixes 3/5] security/apparmor/apparmorfs.c:209:13: warning: 'aa_get_common_ref' defined but not used
Date: Fri, 20 Mar 2026 17:56:11 +0800 [thread overview]
Message-ID: <202603201736.4Hif1yve-lkp@intel.com> (raw)
tree: https://github.com/amir73il/linux vfs-fixes
head: 045aba2b089c3414b0cf3522a43dbfe4b83302ee
commit: f2b9cb55540b0f2da08380cd369a496542fcb717 [3/5] Merge remote-tracking branch 'vfs/vfs-7.1.directory' into next
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260320/202603201736.4Hif1yve-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260320/202603201736.4Hif1yve-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/202603201736.4Hif1yve-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> security/apparmor/apparmorfs.c:209:13: warning: 'aa_get_common_ref' defined but not used [-Wunused-function]
209 | static void aa_get_common_ref(struct aa_common_ref *ref)
| ^~~~~~~~~~~~~~~~~
vim +/aa_get_common_ref +209 security/apparmor/apparmorfs.c
8e135b8aee5a06 John Johansen 2026-03-01 208
8e135b8aee5a06 John Johansen 2026-03-01 @209 static void aa_get_common_ref(struct aa_common_ref *ref)
8e135b8aee5a06 John Johansen 2026-03-01 210 {
8e135b8aee5a06 John Johansen 2026-03-01 211 kref_get(&ref->count);
8e135b8aee5a06 John Johansen 2026-03-01 212 }
8e135b8aee5a06 John Johansen 2026-03-01 213
:::::: The code at line 209 was first introduced by commit
:::::: 8e135b8aee5a06c52a4347a5a6d51223c6f36ba3 apparmor: fix race between freeing data and fs accessing it
:::::: TO: John Johansen <john.johansen@canonical.com>
:::::: CC: John Johansen <john.johansen@canonical.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-20 9:57 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=202603201736.4Hif1yve-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.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.