From: kernel test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-unionfs@vger.kernel.org
Subject: [miklos-vfs:fileattr_v4 22/23] fs/fuse/ioctl.c:403:19: warning: no previous prototype for function 'fuse_priv_ioctl_prepare'
Date: Thu, 8 Apr 2021 14:42:34 +0800 [thread overview]
Message-ID: <202104081431.vKXa7usI-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2889 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git fileattr_v4
head: 621a35401402871cedd0fbd583bb2d0b961af609
commit: 37efe2f3c88fb040c7543f05b72a8c0589bbc447 [22/23] fuse: convert to fileattr
config: x86_64-randconfig-a004-20210407 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 56ea2e2fdd691136d5e6631fa0e447173694b82c)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git/commit/?id=37efe2f3c88fb040c7543f05b72a8c0589bbc447
git remote add miklos-vfs https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git
git fetch --no-tags miklos-vfs fileattr_v4
git checkout 37efe2f3c88fb040c7543f05b72a8c0589bbc447
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/fuse/ioctl.c:403:19: warning: no previous prototype for function 'fuse_priv_ioctl_prepare' [-Wmissing-prototypes]
struct fuse_file *fuse_priv_ioctl_prepare(struct inode *inode)
^
fs/fuse/ioctl.c:403:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
struct fuse_file *fuse_priv_ioctl_prepare(struct inode *inode)
^
static
>> fs/fuse/ioctl.c:414:6: warning: no previous prototype for function 'fuse_priv_ioctl_cleanup' [-Wmissing-prototypes]
void fuse_priv_ioctl_cleanup(struct inode *inode, struct fuse_file *ff)
^
fs/fuse/ioctl.c:414:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void fuse_priv_ioctl_cleanup(struct inode *inode, struct fuse_file *ff)
^
static
2 warnings generated.
vim +/fuse_priv_ioctl_prepare +403 fs/fuse/ioctl.c
402
> 403 struct fuse_file *fuse_priv_ioctl_prepare(struct inode *inode)
404 {
405 struct fuse_mount *fm = get_fuse_mount(inode);
406 bool isdir = S_ISDIR(inode->i_mode);
407
408 if (!S_ISREG(inode->i_mode) && !isdir)
409 return ERR_PTR(-ENOTTY);
410
411 return fuse_file_open(fm, get_node_id(inode), O_RDONLY, isdir);
412 }
413
> 414 void fuse_priv_ioctl_cleanup(struct inode *inode, struct fuse_file *ff)
415 {
416 fuse_file_release(inode, ff, O_RDONLY, NULL, S_ISDIR(inode->i_mode));
417 }
418
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35481 bytes --]
reply other threads:[~2021-04-08 6:43 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=202104081431.vKXa7usI-lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@redhat.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;
as well as URLs for NNTP newsgroup(s).