From: kernel test robot <lkp@intel.com>
To: NeilBrown <neilb@suse.de>
Cc: oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>
Subject: [brauner-github:vfs-6.15.async.dir 4/10] fs/sysv/namei.c:275:27: error: initialization of 'struct dentry * (*)(struct mnt_idmap *, struct inode *, struct dentry *, umode_t)' {aka 'struct dentry * (*)(struct mnt_idmap *, struct inode *, struct dentry *, short unsigned int)'} from incompatible poi...
Date: Fri, 28 Feb 2025 00:03:47 +0800 [thread overview]
Message-ID: <202502272351.BseXPtX2-lkp@intel.com> (raw)
tree: https://github.com/brauner/linux.git vfs-6.15.async.dir
head: d49e14c16a69c5a3989c32142b986cb863c1debe
commit: 10a5b48c3eeb26bc4fa095dca9a6e7c4a89efdf9 [4/10] Change inode_operations.mkdir to return struct dentry *
config: i386-buildonly-randconfig-004-20250227 (https://download.01.org/0day-ci/archive/20250227/202502272351.BseXPtX2-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250227/202502272351.BseXPtX2-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/202502272351.BseXPtX2-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/sysv/namei.c:275:27: error: initialization of 'struct dentry * (*)(struct mnt_idmap *, struct inode *, struct dentry *, umode_t)' {aka 'struct dentry * (*)(struct mnt_idmap *, struct inode *, struct dentry *, short unsigned int)'} from incompatible pointer type 'int (*)(struct mnt_idmap *, struct inode *, struct dentry *, umode_t)' {aka 'int (*)(struct mnt_idmap *, struct inode *, struct dentry *, short unsigned int)'} [-Werror=incompatible-pointer-types]
275 | .mkdir = sysv_mkdir,
| ^~~~~~~~~~
fs/sysv/namei.c:275:27: note: (near initialization for 'sysv_dir_inode_operations.mkdir')
cc1: some warnings being treated as errors
vim +275 fs/sysv/namei.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 265
^1da177e4c3f41 Linus Torvalds 2005-04-16 266 /*
^1da177e4c3f41 Linus Torvalds 2005-04-16 267 * directories can handle most operations...
^1da177e4c3f41 Linus Torvalds 2005-04-16 268 */
c5ef1c42c51b1b Arjan van de Ven 2007-02-12 269 const struct inode_operations sysv_dir_inode_operations = {
^1da177e4c3f41 Linus Torvalds 2005-04-16 270 .create = sysv_create,
^1da177e4c3f41 Linus Torvalds 2005-04-16 271 .lookup = sysv_lookup,
^1da177e4c3f41 Linus Torvalds 2005-04-16 272 .link = sysv_link,
^1da177e4c3f41 Linus Torvalds 2005-04-16 273 .unlink = sysv_unlink,
^1da177e4c3f41 Linus Torvalds 2005-04-16 274 .symlink = sysv_symlink,
^1da177e4c3f41 Linus Torvalds 2005-04-16 @275 .mkdir = sysv_mkdir,
:::::: The code at line 275 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-27 16:07 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=202502272351.BseXPtX2-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=neilb@suse.de \
--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.