Linux Security Modules development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Oxana Kharitonova <webprosto@gmail.com>,
	mic@digikod.net, brauner@kernel.org, viro@zeniv.linux.org.uk,
	gnoack@google.com, utilityemal77@gmail.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-security-module@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, webprosto@gmail.com,
	landlock@lists.linux.dev
Subject: Re: [PATCH v2 2/4] Landlock: Enforce MAKE_REG for POSIX message queue creation
Date: Tue, 3 Nov 2026 10:42:35 +0800	[thread overview]
Message-ID: <202611031036.3r5EL9TN-lkp@intel.com> (raw)
In-Reply-To: <20261102144708.920232-3-webprosto@gmail.com>

Hi Oxana,

kernel test robot noticed the following build warnings:

[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on linus/master next-20261030]
[cannot apply to shuah-kselftest/fixes trace/for-next brauner-vfs/vfs.all v7.3]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Oxana-Kharitonova/ipc-Move-MQUEUE_MAGIC-to-a-shared-header/20261102-144557
base:   https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link:    https://lore.kernel.org/r/20261102144708.920232-3-webprosto%40gmail.com
patch subject: [PATCH v2 2/4] Landlock: Enforce MAKE_REG for POSIX message queue creation
config: s390-defconfig (https://download.01.org/0day-ci/archive/20261103/202611031036.3r5EL9TN-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261103/202611031036.3r5EL9TN-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/202611031036.3r5EL9TN-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> security/landlock/fs.c:1686:51: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
    1686 |                              struct dentry *const dentry, const umode_t)
         |                                                                        ^
   security/landlock/fs.c:2117:30: error: incompatible function pointer types initializing 'int (*)(const struct mnt_idmap *, struct inode *, struct dentry *, umode_t)' (aka 'int (*)(const struct mnt_idmap *, struct inode *, struct dentry *, unsigned short)') with an expression of type 'int (struct inode *const, struct dentry *const, const umode_t)' (aka 'int (struct inode *const, struct dentry *const, const unsigned short)') [-Wincompatible-function-pointer-types]
    2117 |         LSM_HOOK_INIT(inode_create, hook_inode_create),
         |                                     ^~~~~~~~~~~~~~~~~
   include/linux/lsm_hooks.h:141:21: note: expanded from macro 'LSM_HOOK_INIT'
     141 |                 .hook = { .NAME = HOOK }                \
         |                                   ^~~~
   1 warning and 1 error generated.


vim +1686 security/landlock/fs.c

  1679	
  1680	/*
  1681	 * Unlike regular file creation, mq_open(2) calls vfs_mkobj() directly and
  1682	 * therefore does not trigger the path_mknod hook.  Use the mqueuefs mount
  1683	 * associated with the current IPC namespace to recover the parent path.
  1684	 */
  1685	static int hook_inode_create(struct inode *const dir,
> 1686				     struct dentry *const dentry, const umode_t)
  1687	{
  1688		struct ipc_namespace *ipc_ns;
  1689		struct vfsmount *mnt;
  1690		struct path parent;
  1691	
  1692		if (!landlock_is_posix_mqueue_fs(dir))
  1693			return 0;
  1694	
  1695		if (!current->nsproxy)
  1696			return 0;
  1697		ipc_ns = current->nsproxy->ipc_ns;
  1698		if (!ipc_ns)
  1699			return 0;
  1700		mnt = ipc_ns->mq_mnt;
  1701		if (WARN_ON_ONCE(!mnt || mnt->mnt_sb != dir->i_sb))
  1702			return 0;
  1703	
  1704		parent.mnt = mnt;
  1705		parent.dentry = dentry->d_parent;
  1706		return current_check_access_path(&parent, LANDLOCK_ACCESS_FS_MAKE_REG);
  1707	}
  1708	

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

  parent reply	other threads:[~2026-11-03  2:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 14:45 [PATCH v2 0/4] Landlock: Restrict POSIX message queue creation and access Oxana Kharitonova
2026-11-02 14:45 ` [PATCH v2 1/4] ipc: Move MQUEUE_MAGIC to a shared header Oxana Kharitonova
2026-11-02 14:51   ` sashiko-bot
2026-11-02 14:45 ` [PATCH v2 2/4] Landlock: Enforce MAKE_REG for POSIX message queue creation Oxana Kharitonova
2026-11-02 15:06   ` sashiko-bot
2026-11-03  2:42   ` kernel test robot [this message]
2026-11-02 14:45 ` [PATCH v2 3/4] Landlock: Add POSIX message queue scoping Oxana Kharitonova
2026-11-02 15:09   ` sashiko-bot
2026-11-03  4:55   ` kernel test robot
2026-11-03  5:22   ` kernel test robot
2026-11-02 14:46 ` [PATCH v2 4/4] samples/landlock: Add POSIX message queue scoping to sandboxer Oxana Kharitonova
2026-11-02 15:22   ` sashiko-bot

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=202611031036.3r5EL9TN-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brauner@kernel.org \
    --cc=gnoack@google.com \
    --cc=landlock@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mic@digikod.net \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=utilityemal77@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=webprosto@gmail.com \
    /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