From: kernel test robot <lkp@intel.com>
To: Chiara Meiohas <cmeiohas@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Leon Romanovsky <leon@kernel.org>,
Maher Sanalla <msanalla@nvidia.com>,
Edward Srouji <edwards@nvidia.com>
Subject: [leon-rdma:fw-lsm-hook-v2 2/4] security/security.c:5392:1: error: expected identifier or '('
Date: Tue, 10 Mar 2026 06:27:20 +0800 [thread overview]
Message-ID: <202603100634.gK2y4AYT-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git fw-lsm-hook-v2
head: 6ecd3e51800ae840af7be672077ab1e9d0af365e
commit: 59b61e265be95f103df6fa7a195c287b7604dd67 [2/4] lsm: add hook for firmware command validation
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260310/202603100634.gK2y4AYT-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260310/202603100634.gK2y4AYT-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/202603100634.gK2y4AYT-lkp@intel.com/
All errors (new ones prefixed by >>):
>> security/security.c:5392:1: error: expected identifier or '('
5392 | {
| ^
1 error generated.
vim +5392 security/security.c
5375
5376 /**
5377 * security_fw_validate_cmd() - Validate a firmware command
5378 * @in: pointer to the firmware command input buffer
5379 * @in_len: length of the firmware command input buffer
5380 * @dev: device associated with the command
5381 * @class_id: class of the firmware command
5382 * @id: device identifier, specific to the command @class_id
5383 *
5384 * Check permissions before sending a firmware command generated by
5385 * userspace to the device.
5386 *
5387 * Return: Returns 0 if permission is granted.
5388 */
5389 int security_fw_validate_cmd(const void *in, size_t in_len,
5390 const struct device *dev,
5391 enum fw_cmd_class class_id, u32 id);
> 5392 {
5393 if (class_id >= FW_CMD_CLASS_MAX)
5394 return -EINVAL;
5395
5396 return call_int_hook(fw_validate_cmd, in, in_len, dev, class_id, id);
5397 }
5398 EXPORT_SYMBOL_GPL(security_fw_validate_cmd);
5399
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-09 22:27 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=202603100634.gK2y4AYT-lkp@intel.com \
--to=lkp@intel.com \
--cc=cmeiohas@nvidia.com \
--cc=edwards@nvidia.com \
--cc=leon@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=msanalla@nvidia.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.