All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>, linux-fsdevel@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Al Viro <viro@zeniv.linux.org.uk>,
	Amir Goldstein <amir73il@gmail.com>,
	David Howells <dhowells@redhat.com>,
	Yu-li Lin <yulilin@google.com>,
	Chirantan Ekbote <chirantan@chromium.org>
Subject: Re: [PATCH 7/8] vfs: open inside ->tmpfile()
Date: Sat, 17 Sep 2022 09:28:52 +0800	[thread overview]
Message-ID: <202209170929.VcScdpPu-lkp@intel.com> (raw)
In-Reply-To: <20220916194416.1657716-7-mszeredi@redhat.com>

Hi Miklos,

I love your patch! Yet something to improve:

[auto build test ERROR on kdave/for-next]
[also build test ERROR on jaegeuk-f2fs/dev-test linus/master v6.0-rc5]
[cannot apply to viro-vfs/for-next next-20220916]
[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/Miklos-Szeredi/cachefiles-tmpfile-error-handling-cleanup/20220917-034700
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
config: hexagon-randconfig-r041-20220916 (https://download.01.org/0day-ci/archive/20220917/202209170929.VcScdpPu-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 791a7ae1ba3efd6bca96338e10ffde557ba83920)
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
        # https://github.com/intel-lab-lkp/linux/commit/87f47d099f22ea898e5d05215f9b2c4647012001
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Miklos-Szeredi/cachefiles-tmpfile-error-handling-cleanup/20220917-034700
        git checkout 87f47d099f22ea898e5d05215f9b2c4647012001
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from mm/shmem.c:24:
   In file included from include/linux/fs.h:8:
   include/linux/dcache.h:253:30: warning: declaration of 'struct file' will not be visible outside of this function [-Wvisibility]
   extern void d_tmpfile(struct file *, struct inode *);
                                ^
>> mm/shmem.c:2930:13: error: incompatible pointer types passing 'struct file *' to parameter of type 'struct file *' [-Werror,-Wincompatible-pointer-types]
                   d_tmpfile(file, inode);
                             ^~~~
   include/linux/dcache.h:253:36: note: passing argument to parameter here
   extern void d_tmpfile(struct file *, struct inode *);
                                      ^
   1 warning and 1 error generated.
--
   In file included from fs/ext4/namei.c:28:
   In file included from include/linux/fs.h:8:
   include/linux/dcache.h:253:30: warning: declaration of 'struct file' will not be visible outside of this function [-Wvisibility]
   extern void d_tmpfile(struct file *, struct inode *);
                                ^
>> fs/ext4/namei.c:2874:13: error: incompatible pointer types passing 'struct file *' to parameter of type 'struct file *' [-Werror,-Wincompatible-pointer-types]
                   d_tmpfile(file, inode);
                             ^~~~
   include/linux/dcache.h:253:36: note: passing argument to parameter here
   extern void d_tmpfile(struct file *, struct inode *);
                                      ^
   1 warning and 1 error generated.
--
   In file included from fs/ramfs/inode.c:26:
   In file included from include/linux/fs.h:8:
   include/linux/dcache.h:253:30: warning: declaration of 'struct file' will not be visible outside of this function [-Wvisibility]
   extern void d_tmpfile(struct file *, struct inode *);
                                ^
>> fs/ramfs/inode.c:156:12: error: incompatible pointer types passing 'struct file *' to parameter of type 'struct file *' [-Werror,-Wincompatible-pointer-types]
           d_tmpfile(file, inode);
                     ^~~~
   include/linux/dcache.h:253:36: note: passing argument to parameter here
   extern void d_tmpfile(struct file *, struct inode *);
                                      ^
   1 warning and 1 error generated.
--
   In file included from fs/udf/namei.c:22:
   In file included from fs/udf/udfdecl.h:10:
   In file included from include/linux/fs.h:8:
   include/linux/dcache.h:253:30: warning: declaration of 'struct file' will not be visible outside of this function [-Wvisibility]
   extern void d_tmpfile(struct file *, struct inode *);
                                ^
>> fs/udf/namei.c:643:12: error: incompatible pointer types passing 'struct file *' to parameter of type 'struct file *' [-Werror,-Wincompatible-pointer-types]
           d_tmpfile(file, inode);
                     ^~~~
   include/linux/dcache.h:253:36: note: passing argument to parameter here
   extern void d_tmpfile(struct file *, struct inode *);
                                      ^
   1 warning and 1 error generated.


vim +2930 mm/shmem.c

  2912	
  2913	static int
  2914	shmem_tmpfile(struct user_namespace *mnt_userns, struct inode *dir,
  2915		      struct file *file, umode_t mode)
  2916	{
  2917		struct inode *inode;
  2918		int error = -ENOSPC;
  2919	
  2920		inode = shmem_get_inode(dir->i_sb, dir, mode, 0, VM_NORESERVE);
  2921		if (inode) {
  2922			error = security_inode_init_security(inode, dir,
  2923							     NULL,
  2924							     shmem_initxattrs, NULL);
  2925			if (error && error != -EOPNOTSUPP)
  2926				goto out_iput;
  2927			error = simple_acl_create(dir, inode);
  2928			if (error)
  2929				goto out_iput;
> 2930			d_tmpfile(file, inode);
  2931		}
  2932		return finish_tmpfile(file, error);
  2933	out_iput:
  2934		iput(inode);
  2935		return error;
  2936	}
  2937	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  parent reply	other threads:[~2022-09-17  1:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 19:44 [PATCH 1/8] cachefiles: tmpfile error handling cleanup Miklos Szeredi
2022-09-16 19:44 ` [PATCH 2/8] vfs: add tmpfile_open() helper Miklos Szeredi
2022-09-16 19:44 ` [PATCH 3/8] cachefiles: use " Miklos Szeredi
2022-09-16 19:44 ` [PATCH 4/8] ovl: " Miklos Szeredi
2022-09-16 19:44 ` [PATCH 5/8] vfs: make vfs_tmpfile() static Miklos Szeredi
2022-09-16 19:44 ` [PATCH 6/8] vfs: move open right after ->tmpfile() Miklos Szeredi
2022-09-16 19:44 ` [PATCH 7/8] vfs: open inside ->tmpfile() Miklos Szeredi
2022-09-16 22:04   ` kernel test robot
2022-09-17  1:28   ` kernel test robot [this message]
2022-09-17  1:49   ` kernel test robot
2022-09-16 19:44 ` [PATCH 8/8] fuse: implement ->tmpfile() Miklos Szeredi
2022-09-16 21:52   ` Bernd Schubert
2022-09-19  6:30     ` Miklos Szeredi
2022-09-19  7:16       ` Bernd Schubert

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=202209170929.VcScdpPu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=amir73il@gmail.com \
    --cc=chirantan@chromium.org \
    --cc=dhowells@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mszeredi@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yulilin@google.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 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.