linux-kernel.vger.kernel.org archive mirror
 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 2110/2579] include/linux/fscrypt.h:757:37: warning: initialization of 'const struct inode *' from 'int' makes pointer from integer without a cast
Date: Thu, 21 Apr 2022 14:45:08 +0800	[thread overview]
Message-ID: <202204211315.igKpJ2Wz-lkp@intel.com> (raw)

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git sched/headers
head:   49e1ec6c70a6eb4b7de9250a455b8b63eb42afbe
commit: 1cb1e496fc95fd250b11d4ae7bd593cbe22bb5f6 [2110/2579] headers/deps: fs: Optimize <linux/fs.h> dependencies, remove <linux/fs_api.h> inclusion
config: x86_64-randconfig-a013 (https://download.01.org/0day-ci/archive/20220421/202204211315.igKpJ2Wz-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=1cb1e496fc95fd250b11d4ae7bd593cbe22bb5f6
        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 1cb1e496fc95fd250b11d4ae7bd593cbe22bb5f6
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/pci/ fs/crypto/

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 >>):

   In file included from fs/crypto/fscrypt_private.h:14,
                    from fs/crypto/fname.c:23:
   include/linux/fscrypt.h: In function 'fscrypt_dio_supported':
   include/linux/fscrypt.h:757:37: error: implicit declaration of function 'file_inode'; did you mean 'd_inode'? [-Werror=implicit-function-declaration]
     757 |         const struct inode *inode = file_inode(iocb->ki_filp);
         |                                     ^~~~~~~~~~
         |                                     d_inode
>> include/linux/fscrypt.h:757:37: warning: initialization of 'const struct inode *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
   cc1: some warnings being treated as errors


vim +757 include/linux/fscrypt.h

c6c89783eba05a5 Eric Biggers 2022-01-28  753  
c6c89783eba05a5 Eric Biggers 2022-01-28  754  static inline bool fscrypt_dio_supported(struct kiocb *iocb,
c6c89783eba05a5 Eric Biggers 2022-01-28  755  					 struct iov_iter *iter)
c6c89783eba05a5 Eric Biggers 2022-01-28  756  {
c6c89783eba05a5 Eric Biggers 2022-01-28 @757  	const struct inode *inode = file_inode(iocb->ki_filp);
c6c89783eba05a5 Eric Biggers 2022-01-28  758  
c6c89783eba05a5 Eric Biggers 2022-01-28  759  	return !fscrypt_needs_contents_encryption(inode);
c6c89783eba05a5 Eric Biggers 2022-01-28  760  }
c6c89783eba05a5 Eric Biggers 2022-01-28  761  

:::::: The code at line 757 was first introduced by commit
:::::: c6c89783eba05a5e159b07cfd8c68d841cc5de42 fscrypt: add functions for direct I/O support

:::::: TO: Eric Biggers <ebiggers@google.com>
:::::: CC: Eric Biggers <ebiggers@google.com>

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

                 reply	other threads:[~2022-04-21  6:48 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=202204211315.igKpJ2Wz-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;
as well as URLs for NNTP newsgroup(s).