From: kernel test robot <lkp@intel.com>
To: jason.zeng@intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [bytedance:6.6-velinux 87/87] security/integrity/ima/ima_queue.c:218:1: warning: label 'try_add_ima_entry' defined but not used
Date: Thu, 18 Dec 2025 21:13:40 +0800 [thread overview]
Message-ID: <202512182112.dFUFExFT-lkp@intel.com> (raw)
tree: https://github.com/bytedance/kernel.git 6.6-velinux
head: 8ba291f6d44d3336d9ef45cc81cf3f5a000bf246
commit: a5f2c036d5b2b8c2ac0eebaa11a6c8999f1bcd95 [87/87] bytedance: ima: fix UAF issue after ima_tdx_extend failed.
config: x86_64-bytedance-6.6-velinux-kselftests (https://download.01.org/0day-ci/archive/20251218/202512182112.dFUFExFT-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251218/202512182112.dFUFExFT-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/202512182112.dFUFExFT-lkp@intel.com/
All warnings (new ones prefixed by >>):
security/integrity/ima/ima_queue.c: In function 'ima_add_template_entry':
>> security/integrity/ima/ima_queue.c:218:1: warning: label 'try_add_ima_entry' defined but not used [-Wunused-label]
218 | try_add_ima_entry:
| ^~~~~~~~~~~~~~~~~
vim +/try_add_ima_entry +218 security/integrity/ima/ima_queue.c
209
210 tpmresult = ima_pcr_extend(digests_arg, entry->pcr);
211 if (tpmresult != 0) {
212 snprintf(tpm_audit_cause, AUDIT_CAUSE_LEN_MAX, "TPM_error(%d)",
213 tpmresult);
214 audit_cause = tpm_audit_cause;
215 audit_info = 0;
216 }
217
> 218 try_add_ima_entry:
219 if (!tpmresult) {
220 /* Allocate memory in advance and it won't fail. */
221 ima_add_digest_entry(entry,
222 !IS_ENABLED(CONFIG_IMA_DISABLE_HTABLE), qe);
223 } else {
224 kfree(qe);
225 }
226
227 out:
228 mutex_unlock(&ima_extend_list_mutex);
229 integrity_audit_msg(AUDIT_INTEGRITY_PCR, inode, filename,
230 op, audit_cause, result, audit_info);
231 return result;
232 }
233
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-18 13:14 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=202512182112.dFUFExFT-lkp@intel.com \
--to=lkp@intel.com \
--cc=jason.zeng@intel.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.