public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [mingo-tip:sched/headers 2441/2579] include/linux/fs_api.h:424:29: error: conflicting types for 'file_inode'; have 'struct inode *(const struct file *)'
Date: Sun, 24 Apr 2022 04:55:13 +0800	[thread overview]
Message-ID: <202204240431.wESdhsIX-lkp@intel.com> (raw)

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git sched/headers
head:   49e1ec6c70a6eb4b7de9250a455b8b63eb42afbe
commit: 5e5b9f1427ab55c511d68e2ee5471cbeabf50830 [2441/2579] headers/deps: mm: Optimize <linux/pagemap.h> dependencies
config: x86_64-randconfig-a015 (https://download.01.org/0day-ci/archive/20220424/202204240431.wESdhsIX-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git/commit/?id=5e5b9f1427ab55c511d68e2ee5471cbeabf50830
        git remote add mingo-tip git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git
        git fetch --no-tags mingo-tip sched/headers
        git checkout 5e5b9f1427ab55c511d68e2ee5471cbeabf50830
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

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

All errors (new ones prefixed by >>):

   In file included from fs/ubifs/ubifs.h:40,
                    from fs/ubifs/file.c:40:
   include/linux/fscrypt.h: In function 'fscrypt_dio_supported':
   include/linux/fscrypt.h:758:37: error: implicit declaration of function 'file_inode'; did you mean 'folio_inode'? [-Werror=implicit-function-declaration]
     758 |         const struct inode *inode = file_inode(iocb->ki_filp);
         |                                     ^~~~~~~~~~
         |                                     folio_inode
   include/linux/fscrypt.h:758:37: warning: initialization of 'const struct inode *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
   In file included from include/linux/backing-dev-api.h:16,
                    from include/linux/writeback_api.h:16,
                    from fs/ubifs/file.c:42:
   include/linux/fs_api.h: At top level:
>> include/linux/fs_api.h:424:29: error: conflicting types for 'file_inode'; have 'struct inode *(const struct file *)'
     424 | static inline struct inode *file_inode(const struct file *f)
         |                             ^~~~~~~~~~
   In file included from fs/ubifs/ubifs.h:40,
                    from fs/ubifs/file.c:40:
   include/linux/fscrypt.h:758:37: note: previous implicit declaration of 'file_inode' with type 'int()'
     758 |         const struct inode *inode = file_inode(iocb->ki_filp);
         |                                     ^~~~~~~~~~
   cc1: some warnings being treated as errors


vim +424 include/linux/fs_api.h

0f5d0a0fe62409 Ingo Molnar 2022-04-16  423  
0f5d0a0fe62409 Ingo Molnar 2022-04-16 @424  static inline struct inode *file_inode(const struct file *f)
0f5d0a0fe62409 Ingo Molnar 2022-04-16  425  {
0f5d0a0fe62409 Ingo Molnar 2022-04-16  426  	return f->f_inode;
0f5d0a0fe62409 Ingo Molnar 2022-04-16  427  }
0f5d0a0fe62409 Ingo Molnar 2022-04-16  428  

:::::: The code at line 424 was first introduced by commit
:::::: 0f5d0a0fe6240979a116fdd86cc2997879173bff headers/deps: fs: Split <linux/fs.h> into <linux/fs_types.h> and <linux/fs_api.h>

:::::: TO: Ingo Molnar <mingo@kernel.org>
:::::: CC: Ingo Molnar <mingo@kernel.org>

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

                 reply	other threads:[~2022-04-23 20:55 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=202204240431.wESdhsIX-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    /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