mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: " Mickaël Salaün " <mic@digikod.net>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: security/landlock/fs.c:1339:18: sparse: sparse: Initializer entry defined twice
Date: Sat, 17 Jan 2026 12:57:27 +0800	[thread overview]
Message-ID: <202601171241.AOq0Obg0-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   39d3389331abd712461f50249722f7ed9d815068
commit: c56f649646ecec3dd1a2e400e6e5ec83439d940f landlock: Log mount-related denials
date:   10 months ago
config: arm-randconfig-r132-20260117 (https://download.01.org/0day-ci/archive/20260117/202601171241.AOq0Obg0-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260117/202601171241.AOq0Obg0-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/202601171241.AOq0Obg0-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> security/landlock/fs.c:1339:18: sparse: sparse: Initializer entry defined twice
   security/landlock/fs.c:1340:26: sparse:   also defined here
   security/landlock/fs.c:1353:18: sparse: sparse: Initializer entry defined twice
   security/landlock/fs.c:1354:26: sparse:   also defined here

vim +1339 security/landlock/fs.c

  1333	
  1334	static void
  1335	log_fs_change_topology_path(const struct landlock_cred_security *const subject,
  1336				    size_t handle_layer, const struct path *const path)
  1337	{
  1338		landlock_log_denial(subject, &(struct landlock_request) {
> 1339			.type = LANDLOCK_REQUEST_FS_CHANGE_TOPOLOGY,
  1340			.audit = {
  1341				.type = LSM_AUDIT_DATA_PATH,
  1342				.u.path = *path,
  1343			},
  1344			.layer_plus_one = handle_layer + 1,
  1345		});
  1346	}
  1347	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-01-17  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-17  4:57 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-13 19:52 kernel test robot

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=202601171241.AOq0Obg0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®